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/dwarvesf/dwarves-kit/agents-mdgit clone --depth 1 https://github.com/dwarvesf/dwarves-kitWhat 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.04088 | $0.04088 |
| Opus 5 | $0.02044 | $0.02044 |
| Sonnet 5 | $0.00818 | $0.00818 |
| Haiku 4.5 | $0.00409 | $0.00409 |
Grade A, and why
dwarves-kit 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.
How it starts
The opening of the file, as written. The whole thing — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md: the operating layer
Tool-agnostic front door. Any agent runtime (Claude Code, Codex, Gemini, a human) reads this first to learn how work is done in this repo. It carries the portable operate-contract: what to read, how to run a unit of work, when work is done, and when to stop and ask.
Enforcement boundary (read this first)
This file is a contract, not a guardrail. Enforcement is Claude-Code-only: the
hooks (safety-gate, push-to-main blocker, anti-rationalization Stop hook, the
verification pipeline) are what actually block bad outcomes, and they run only
under Claude Code. Under any other runtime (Codex, Gemini, a bare LLM)
AGENTS.md is advisory only: it tells an agent what to do, but nothing
enforces it. Do not assume the guardrails are portable. They are not, until the
v3.x multi-runtime agent-hook work lands. See docs/PHILOSOPHY.md (honesty rule:
never over-claim portable enforcement) and CLAUDE.md for the CC-specific layer
(hooks, slash commands, plugin). The full layering contract, which hook
backstops what and why (hard / advisory / convenience), is
docs/architecture.md "Hook fallback layer".
The rest of this file is four portable zones. The goal-crafter
(commands/assign.md) projects them into a six-section /goal (see "How a goal
is composed" at the end).
1. Read in this order
Orient before you touch anything. Read top to bottom; stop when you have enough.
- AGENTS.md (this file) - how work is done here; the operate-contract.
- CLAUDE.md - the Claude-Code layer: stack, structure, rules, hooks, commands, plugin.
- docs/specs/SPEC-NNN-.md - the active spec; the shared contract for the cycle. Read its
## Verificationand## After statebefore implementing. - docs/architecture.md / WORKFLOW.md / docs/data-flow.md - reference, not required per task. Read
docs/architecture.mdfor how the pieces fit;docs/data-flow.mdfor how DATA moves (the signal path telemetry -> proposal -> board, the ledger write/read paths, the module map); readWORKFLOW.mdfor the lanes and the gate at each phase boundary, and its "Mega-goal delegate execution" section for how a multi-sub-goal mega-goal run dispatches (delegate mode: one fresh headless session per sub-goal;/goalstays the official outer loop either way).
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 · 185 lines · 4,088 tokens per session scan A 15744d73916c
dwarves-kit AGENTS.md is an instructions file published in the GitHub repository dwarvesf/dwarves-kit (11 stars, last pushed 2d ago), licensed MIT. It adds 4,088 tokens to every session, about $0.0204 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
gangsta AGENTS.md
Instructions for kucherenko/gangsta, covering contributing to gangsta, what this is, what will not be accepted, skill changes and the laws apply to contributors too.
featherspec memory-bank.instructions.md
FeatherSpec Memory Bank writing rules (thin loader).
airflow CLAUDE.md
Claude Code instructions for apache/airflow, a project described as: Apache Airflow - A platform to programmatically author, schedule, and monitor workflows.
gangsta GEMINI.md
Instructions for kucherenko/gangsta, a project described as: AI agentic skills framework for spec-driven development, built on the organizational model of mafia.
hashloom CLAUDE.md
Claude Code instructions for davet47/hashloom, covering working rules for hashloom, git is the user's, scope discipline, hashloom develops on hashloom and definition of done: >5x token reduction.
specs-driven-development-spring-angular frontend-code.instructions.md
Frontend code guardrails for Angular implementation, testing, and accessibility.