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 commands/dwarvesf/dwarves-kit/adoptgit 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.00060 | $0.00683 |
| Opus 5 | $0.00030 | $0.00342 |
| Sonnet 5 | $0.00012 | $0.00137 |
| Haiku 4.5 | $0.00006 | $0.00068 |
Grade A, and why
adopt 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are adopting a repo into the dwarves-kit operating layer. This installs the operate-contract so that, from now on, an agent working in that repo classifies the work and picks a lane before coding, and the ship-gate engages on push.
Run
$ARGUMENTS may name a target dir (default: the repo root), --check (status only), or
--with <a,b,c> (seed these modules true in a FRESH .kit.toml; ignored once one exists).
-
Resolve the target: default
.(git rev-parse --show-toplevel). -
Run the driver (idempotent, non-destructive):
bash "${CLAUDE_PLUGIN_ROOT:-$HOME/.claude/dwarves-kit}/lib/adopt.sh" [--check] [--with <a,b,c>] <target> -
Report what it created (or that the repo was already adopted). Tell the user the one next step: open a session in the adopted repo and run
/kit:startto classify the first task.
What adoption installs
AGENTS.md-- the operate-contract (read-first).- a
CLAUDE.mdloader pointer (Claude Code auto-loads CLAUDE.md, not AGENTS.md). WORKFLOW.md-- a pointer to the installed kit's lane x phase matrix (not a 49KB copy).docs/verification/README.md-- the proof marker that makes the ship-gate engage..kit.toml-- an OPT-IN starter override of the kit-root defaults (SPEC-192). Created only on a fresh adopt (never overwritten afterward);--withseeds the named modulestrueinstead of inheriting the kit-root default. Edit[modules]any time and re-run/kit:adopt(or--refresh) to re-wire..claude/settings.jsonhook entries for this project's currently-enabled hook-bearing modules (board,session,advisor,cosmetic) -- a targeted jq MERGE, re-wired on every adopt run from the project's CURRENT.kit.toml, never a wholesale file rewrite. Command/skill modules (queue,stats,quiz_gate,weekend_batch,bridge) need no settings.json entry.
The classifiers (lane-classify, task-type-classify, proof-gate) run from the installed kit;
adoption wires the contract to reference them. It never copies the engine.
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 · 48 lines · 60 tokens per session scan A 829e1ae89157
adopt is a command published in the GitHub repository dwarvesf/dwarves-kit (11 stars, last pushed 2d ago), licensed MIT. It adds 60 tokens to every session and 683 once invoked, about $0.0003 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 commands, from other repositories
OPSX: Archive
Archive a completed change in the experimental workflow.
OPSX: Explore
Enter explore mode - think through ideas, investigate problems, clarify requirements.
OPSX: Propose
Propose a new change - create it and generate all artifacts in one step.
OPSX: Sync
Sync delta specs from a change to main specs.
OPSX: Apply
Implement tasks from an OpenSpec change (Experimental).
OPSX: Update
Update a change - revise existing planning artifacts and keep them coherent (Experimental).