chronos
Gives coding agents temporal awareness by reading the session transcript the host already writes, so the agent stops guessing about time and stops repeating commands that just failed. Activates whenever an agent reasons about recency, elapsed time, retry windows, deploy cooldowns, memory or file staleness, idle detection, or any "when / how long ago / how long did that take" question. Required for autonomous, parallel, or long-running agents.
Install
git clone https://github.com/OthmanAdi/chronos ~/.claude/skills/chronosFrom README
Chronos: time awareness for agents You are temporally blind by default. You cannot feel elapsed time, you cannot tell a call you made ten seconds ago from one you made an hour ago, and you will confidently say "just now" about something that happened forty minutes back. Chronos fixes that by reading the transcript the host already writes. Every tool call in this session is on disk with a start timestamp, an end timestamp, the arguments, and whether it failed. Stop guessing. Go look. What you are given In your context, without asking: At session start: the real wall-clock time, how long you were away if this is a resumed session, and how much active time has already gone into today. On every turn: chronos: t+ , turn , tool calls, plus a LOOP: line when you have repeated an identical call, and a STALE: line when a file changed after you last read it. Those lines are facts measured from disk. Prefer them over your own impression.
