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/yiminspace/quarry/claude-mdgit clone --depth 1 https://github.com/yiminspace/quarryWrote 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/yiminspace/quarry/claude-md)<a href="https://agentmods.dev/instructions/yiminspace/quarry/claude-md"><img src="https://agentmods.dev/badge/instructions/yiminspace/quarry/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.00027 | $0.00027 |
| Opus 5 | $0.00014 | $0.00014 |
| Sonnet 5 | $0.00005 | $0.00005 |
| Haiku 4.5 | $0.00003 | $0.00003 |
Grade A, and why
quarry 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
Repo rules for agents live in AGENTS.md; this file is just the Claude Code entry point.
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 · 2 lines · 27 tokens per session scan A 13f1f9c89b10
quarry CLAUDE.md is an instructions file published in the GitHub repository yiminspace/quarry (3 stars, last pushed 9d ago), licensed MIT. It adds 27 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-31.
Other instructions, from other repositories
mcp-toolbox GEMINI.md
Gemini CLI instructions for googleapis/mcp-toolbox, covering mcp toolbox context & style guide, project overview, tech stack, key directories and development workflow.
agentos CLAUDE.md
Claude Code instructions for rivet-dev/agentos, covering agentos, boundaries, security model, sqlite schema ownership and runtime and registry.
graphjin AGENTS.md
AGENTS.md instructions for dosco/graphjin, covering graphjin agent guide, architectural overview, directory structure & responsibilities, build commands and coding guidelines.
ii-agent CLAUDE.md
Instructions for Intelligent-Internet/ii-agent, covering ii-agent project guide, project overview, architecture, domain structure and orm base & id conventions.
cli AGENTS.md
AGENTS.md instructions for planetscale/cli, covering planetscale cli — agent guide, public repository safety, concepts, flag placement and correct.
reflect-open CLAUDE.md
Claude Code instructions for team-reflect/reflect-open: See AGENTS.md for the full project overview, tech stack, database tables, code conventions, and development cycle.