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/0xjunha/darc/claude-mdgit clone --depth 1 https://github.com/0xjunha/darcWrote 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/0xjunha/darc/claude-md)<a href="https://agentmods.dev/instructions/0xjunha/darc/claude-md"><img src="https://agentmods.dev/badge/instructions/0xjunha/darc/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.00039 | $0.00039 |
| Opus 5 | $0.00019 | $0.00019 |
| Sonnet 5 | $0.00008 | $0.00008 |
| Haiku 4.5 | $0.00004 | $0.00004 |
Grade A, and why
darc 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
Read AGENTS.md and follow instructions.
Treat AGENTS.md as the authoritative policy file.
Read it before planning, editing, testing, or committing.
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 · 5 lines · 39 tokens per session scan A 99c0cb5faa28
darc CLAUDE.md is an instructions file published in the GitHub repository 0xjunha/darc (11 stars, last pushed 2mo ago), licensed MIT. It adds 39 tokens to every session, about $0.0002 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
Zuiti-Desktop AGENTS.md
Instructions for ZuiTiti/Zuiti-Desktop, covering agents.md, 项目概览, 目录地图, 运行命令 and 编码约定.
langgraph AGENTS.md
AGENTS.md instructions for langchain-ai/langgraph, covering agents instructions, corridor security analysis, libraries and dependency map.
hatch3r CLAUDE.md
Claude Code instructions for hatch3r/hatch3r, covering hatch3r — development instructions, architecture, development commands, two-axis pillar framework (2.0.0) and orchestrator self-discipline (bypass protection).
aeon CLAUDE.md
Instructions for aeonfun/aeon, covering aeon, how aeon works, strategy, voice and soul file hierarchy (read in this order).
ken CLAUDE.md
Instructions for townsendmerino/ken, covering claude.md, what this is, repository ownership (read this first), commands and embedding parity & golden fixtures (now in aikit).
AI-System-Design-Consultant CLAUDE.md
Instructions for deepanshu2711/AI-System-Design-Consultant, covering claude.md, what this is, running it, load-bearing typos — do not "fix" these paths and agent node pattern.