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/jcottam/agent-resources/claude-mdgit clone --depth 1 https://github.com/jcottam/agent-resourcesWrote 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/jcottam/agent-resources/claude-md)<a href="https://agentmods.dev/instructions/jcottam/agent-resources/claude-md"><img src="https://agentmods.dev/badge/instructions/jcottam/agent-resources/claude-md.svg" alt="Measured on agentmods" 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 | $0.00018 | $0.00018 |
| Opus 5 | $0.00009 | $0.00009 |
| Sonnet 5 | $0.00004 | $0.00004 |
| Haiku 4.5 | $0.00002 | $0.00002 |
Grade A, and why
agent-resources 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 4d 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
See AGENTS.md for project conventions and contributing guidelines.
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.
- 4d ago First seen · 2 lines · 18 tokens per session scan A 937b0f8dfd4a
agent-resources CLAUDE.md is an instructions file published in the GitHub repository jcottam/agent-resources (30 stars, last pushed 28d ago), licensed MIT. It adds 18 tokens to every session, about $0.0001 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
ai-rules-sync AGENTS.md
Instructions for lbb00/ai-rules-sync, covering agents instructions, project overview, tech stack, key features and directory structure.
openehr-assistant-plugin AGENTS.md
Instructions for Cadasto/openehr-assistant-plugin, covering ai guidelines: openehr assistant plugin, project overview, domain context, companion mcp server and calling conventions the server enforces.
rules-for-ai AGENTS.md
Instructions for hashiiiii/rules-for-ai, covering agents, language, git, issues and pull requests.
aiops AGENTS.md
Instructions for yugasun/aiops, covering aiops — agent definitions, lean discipline, delivery sequence, dispatch by task type and agents.
aiops copilot-instructions.md
Instructions for yugasun/aiops, covering copilot instructions, >, lean, ladder and rules.
aiops CLAUDE.md
Instructions for yugasun/aiops, covering claude.md — aiops repo conventions, file size limit, language and target project conventions.