Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/cote-star/agent-context/agents-mdgit clone --depth 1 https://github.com/cote-star/agent-contextWhat 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 | $0.00074 | $0.00074 |
| Opus 5 | $0.00037 | $0.00037 |
| Sonnet 5 | $0.00015 | $0.00015 |
| Haiku 4.5 | $0.00007 | $0.00007 |
Grade A, and why
agent-context 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 2d 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.
What it actually says
- Read .agent-context/current/routes.json to identify task type
- Load contracts from .agent-context/current/completeness_contract.json + .agent-context/current/search_scope.json
- Search ONLY within scoped directories defined in search_scope.json
- Do not open repo source files before step 3
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.
- 2d ago First seen · 7 lines · 74 tokens per session scan A d6c094db351a
agent-context AGENTS.md is an instructions file published in the GitHub repository cote-star/agent-context (2 stars, last pushed 2mo ago), licensed MIT. It adds 74 tokens to every session, about $0.0004 per session on Opus 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
vitaecontext AGENTS.md
AGENTS.md instructions for vitaecontext/vitaecontext, covering agents.md, scope, start here, source of truth and brand contract.
vitaecontext copilot-instructions.md
Copilot instructions for vitaecontext/vitaecontext, covering repository instructions for github copilot, repository model, coding and documentation rules and validation.
vitaecontext GEMINI.md
Gemini CLI instructions for vitaecontext/vitaecontext, covering vitaecontext, module map and runtime loading.
okp AGENTS.md
Instructions for talesofai/okp, covering agents.md — project conventions for okp, tech stack, architecture, api 端点 and data model (postgresql).
project-tiny-context-harness AGENTS.md
Instructions for Seven128/project-tiny-context-harness, covering project agent overlay, 本仓库 authoring 例外, minimal context harness protocol, shared engineering quality obligation and default workflow contract.
structured-context-spec CLAUDE.md
Instructions for tim-mccrimmon/structured-context-spec, covering claude.md, structured context specification (scs) — project context, what this project is, repository structure and tools & development commands.