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/dark-builders/darq/agents-mdgit clone --depth 1 https://github.com/dark-builders/darqWhat 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.00129 | $0.00129 |
| Opus 5 | $0.00064 | $0.00064 |
| Sonnet 5 | $0.00026 | $0.00026 |
| Haiku 4.5 | $0.00013 | $0.00013 |
Grade A, and why
darq 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
AGENTS.md
For project context, conventions, architecture, and implementation rules, see:
- CLAUDE.md — Project overview, build commands, workspace structure, architecture, error handling, tech stack decisions
- docs/index.md — Documentation index
- docs/agent-rules.md — Comprehensive implementation rules for AI agents (runtime constraints, framework patterns, testing, code quality, dev workflow, anti-patterns, security)
Subfolder AGENTS.md files contain directory-scoped guidance only.
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 · 10 lines · 129 tokens per session scan A 420dc9b1825b
darq AGENTS.md is an instructions file published in the GitHub repository dark-builders/darq (10 stars, last pushed 4mo ago), licensed MIT. It adds 129 tokens to every session, about $0.0006 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
revdiff CLAUDE.md
Instructions for umputun/revdiff, covering revdiff, commands, project structure, architecture principles and config.
cctop AGENTS.md
Instructions for st0012/cctop, covering agents.md - development guide for cctop, scope and sources, required development rules, driver workflow and github and pr rules.
toh-framework CLAUDE.md
Instructions for wasintoh/toh-framework, covering claude.md — toh framework (repo development guide), what this is, everyday commands, verification protocol and single source, transformed per ide.
examples CLAUDE.md
Claude Code instructions for rossoctl/examples, covering claude.md - agent examples, repository structure, key commands, code style and dco sign-off (mandatory).
agent-rules child-process.instructions.md
Instructions for lirantal/agent-rules, covering system processes secure coding guidelines, your mission and spawning system processes.
claude-code-templates CLAUDE.md
Instructions for Justdvp/claude-code-templates, covering claude.md, project overview, development commands, package management and application commands.