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/douglasmonsky/codex-usage-tracker/claude-mdgit clone --depth 1 https://github.com/douglasmonsky/codex-usage-trackerWhat 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.00082 | $0.00082 |
| Opus 5 | $0.00041 | $0.00041 |
| Sonnet 5 | $0.00016 | $0.00016 |
| Haiku 4.5 | $0.00008 | $0.00008 |
Grade A, and why
codex-usage-tracker CLAUDE.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 3d 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
Claude Code Instructions
Read and follow AGENTS.md before changing this repository.
The task-specific GitNexus workflows under .claude/skills/gitnexus/ are
repository-local reference material. Load only the skill matching the current
task. Refresh the graph with gitnexus analyze --index-only . so routine
indexing does not rewrite repository guidance.
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.
- 3d ago First seen · 9 lines · 82 tokens per session scan A 260a18149de8
codex-usage-tracker CLAUDE.md is an instructions file published in the GitHub repository douglasmonsky/codex-usage-tracker (193 stars, last pushed 13d ago), licensed MIT. It adds 82 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-30.
Other instructions, from other repositories
GameStudio-CodexKIT AGENTS.md
Instructions for hoatv2211/GameStudio-CodexKIT, covering gamestudio-codexkit operating contract, active sources of truth, primary distribution, repository-local maintenance and evidence.
simple-man AGENTS.md
Instructions for Maksim-Burtsev/simple-man, a project described as: Cut the chatter. Keep the work. A measured communication policy for coding agents: −32% output tokens, zero lost facts.
model-economy AGENTS.md
Instructions for BottleYo/model-economy, covering model economy 仓库协作规则, 语言与定位, 开发边界 and 验证.
windows-appshot-codex AGENTS.md
AGENTS.md instructions for josephbartlett/windows-appshot-codex, covering agent instructions, project shape, safety rules, review gate and validation.
Skill-RSI AGENTS.md
AGENTS.md instructions for justinwetch/Skill-RSI, covering skill rsi agent setup guide, core rule, agent-assisted setup, opening skill rsi and what not to do during setup.
simple-man CLAUDE.md
Instructions for Maksim-Burtsev/simple-man, a project described as: Cut the chatter. Keep the work. A measured communication policy for coding agents: −32% output tokens, zero lost facts.