Borrowing it
Nothing to install: this file belongs to OthmanAdi/chronos. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/OthmanAdi/chronos/main/AGENTS.mdgit clone --depth 1 https://github.com/OthmanAdi/chronosWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/othmanadi/chronos/agents-md)<a href="https://agentmods.dev/instructions/othmanadi/chronos/agents-md"><img src="https://agentmods.dev/badge/instructions/othmanadi/chronos/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/othmanadi/chronos/agents-md"><img src="https://agentmods.dev/badge/instructions/othmanadi/chronos/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00762 | $0.00762 |
| Opus 5.5 | $0.00305 | $0.00305 |
| Sonnet 5.5 | $0.00152 | $0.00152 |
| Haiku 4.5 | $0.00076 | $0.00076 |
Grade A, and why
chronos AGENTS.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
chronos: time awareness for agents
Mirror of SKILL.md for agents that read AGENTS.md. Same rules, condensed.
You cannot feel elapsed time. Every tool call this session made is on disk with a start timestamp, an end timestamp, its arguments and whether it failed. Read it instead of guessing.
Getting the facts
chronos report where this session's time went (pass --session to pick one)
chronos when <text> when you last ran something matching <text>
chronos today active time across every session today
chronos report --json the same data, machine readable
On a host without chronos hooks, gather the facts yourself and say that you did:
| Need | POSIX | PowerShell |
|---|---|---|
| Now, UTC | date -u +"%Y-%m-%dT%H:%M:%SZ" |
Get-Date -Format o |
| File mtime | stat -c %Y f (GNU), stat -f %m f (BSD) |
(Get-Item f).LastWriteTimeUtc |
| Last commit | git log -1 --format=%cI -- <path> |
same |
The seven rules
-
Before retrying a failed call. Same tool, same arguments, failed under 60 seconds ago: change the approach. Nothing external changed in 60 seconds. 60 seconds to 10 minutes: one retry, and say what you expect to differ. Over 10 minutes: re-running is reasonable. Deploys and CI triggers included.
-
Before trusting something you already looked at. Stale after: 5 minutes for
git status, processes and environment; 1 hour or any write for a file you read; 7 days for persistent memory; 5 minutes for API responses; any source change for build and test results. Your own earlier claim: always verify. -
Before summarising. Under 5 minutes, answer with no recap. 5 to 30 minutes, one paragraph. Over 30 minutes, use
chronos reportand its real numbers. -
Before something long or destructive. If recent runs of a command are each well above its average, something is degrading. Say so rather than waiting.
-
Idle loops. Past the idle threshold with no user input while looping unattended: stop, summarise, list open decisions, ask. Always escalate past two hours of session time with no user input.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago Changed · +13 lines · +185 tokens per session 60b7b445100e
- 1mo ago First seen · 52 lines · 577 tokens per session scan A 83d32209b9d8
chronos AGENTS.md is an instructions file published in the GitHub repository OthmanAdi/chronos (3 stars, last pushed 1mo ago), licensed MIT. It adds 762 tokens to every session, about $0.0030 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).