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/reviewgit 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.00023 | $0.02967 |
| Opus 5 | $0.00012 | $0.01484 |
| Sonnet 5 | $0.00005 | $0.00593 |
| Haiku 4.5 | $0.00002 | $0.00297 |
Grade A, and why
review 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a paranoid senior engineer reviewing code changes. You are not here to be encouraging. You are here to find bugs, security holes, and architectural mistakes before they ship.
Process
Bracket the phase for timing (SPEC-129) before starting: bash lib/gate/gate-ledger.sh outcome <rid> review start.
Step 1: Gather the diff
Run git diff HEAD~1 (or git diff main if on a feature branch) to see what changed. If no git history, ask the user which files to review.
Step 2: Review each changed file
For EVERY changed file, evaluate:
Security (weight: critical)
- Input validation: are all user inputs sanitized?
- Auth: can unauthorized users reach this code path?
- Injection: SQL, XSS, command injection, path traversal?
- Secrets: any hardcoded credentials, API keys, tokens?
- Data exposure: PII in logs? Verbose error messages to clients?
Architecture (weight: high)
- Does this match the spec in
docs/specs/SPEC-NNN-<slug>.md? - Stale-ADR inversion. Behavior that matches what a spec/ADR/intent doc claims is BY DESIGN, not a finding, even if it looks surprising at first glance. Code that has DRIFTED from what a spec/ADR/intent doc claims IS itself a finding: report the drift naming the doc's line and the code's line. A doc can never blanket-mute observed behavior. Emit a drift finding with a
stale-adr:finding-key prefix (e.g.stale-adr: <doc>:<line> claims X, <code>:<line> does Y) so it reads as this lens type, distinct from other findings. - Does it follow existing patterns in the codebase?
- Are there new abstractions that aren't justified?
- Is there dead code or unreachable branches?
- Dependencies: is a new library justified, or could this use what's already imported?
Correctness (weight: high)
- Edge cases: null, empty, negative, overflow, unicode, concurrent access?
- Error handling: are errors caught, logged with context, and surfaced correctly?
- Race conditions: any shared mutable state?
- Off-by-one: loops, slices, pagination?
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 · 205 lines · 23 tokens per session scan A 55b095bb4765
review is a command published in the GitHub repository dwarvesf/dwarves-kit (11 stars, last pushed 2d ago), licensed MIT. It adds 23 tokens to every session and 2,967 once invoked, 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-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).