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/quiz-gategit clone --depth 1 https://github.com/dwarvesf/dwarves-kitWrote 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/commands/dwarvesf/dwarves-kit/quiz-gate)<a href="https://agentmods.dev/commands/dwarvesf/dwarves-kit/quiz-gate"><img src="https://agentmods.dev/badge/commands/dwarvesf/dwarves-kit/quiz-gate.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.00065 | $0.01270 |
| Opus 5 | $0.00032 | $0.00635 |
| Sonnet 5 | $0.00013 | $0.00254 |
| Haiku 4.5 | $0.00006 | $0.00127 |
Grade A, and why
quiz-gate 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 4d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the understanding-gate NUDGE (ADR-0031 §2/§3, the AFTER gate's speed regulator). At the merge
boundary of a gate/gated-final PR, when a change is BOTH significant AND understanding-worthy, you offer
the human a 5-question quiz built from the actual change BEFORE they click-to-merge. $ARGUMENTS is the
change under merge (a commit / PR / spec ref) and its run id (<rid>).
This gates the human's ATTENTION, never the merge. It is a NUDGE (ADR-0031 Refinement point 3): a waved change still merges; you never hard-block a correct build. The only real failure is UNTRACKED debt, so all three responses are recorded.
The two hard constraints (do not violate)
- Grounded in the DIFF + recorded test results, NEVER the agent's narrative (Litt's plausible-but-wrong
caveat). The questions come from
lib/gate/quiz-gate.sh questions <ref>, whose only input is a git ref , there is no narrative channel, so a false story physically cannot leak in. Never hand-write quiz questions from memory, the commit message, or what you "meant" to do. If the commit message contradicts the diff, the diff wins. - Route through
deep-understand, do not build a second quiz. The kit builds the QUESTIONS and dispatches; thedeep-understandskill runs the AskUserQuestion mastery gate (shuffled answer slots, per-item gate on a demonstrated answer). The kit scores nothing.
Process
Step 1: Decide whether to tap (keyed on the SPEC-123 verdict)
Only a tap verdict (significant AND understanding-worthy) on a gate/gated-final PR is ever nudged , the
anti-fatigue guard. A significant-but-low-worthiness change (wave) or a not-significant change is NEVER
quizzed (it is already logged silently by SPEC-123's significance-classify record, wired into /kit:ship
Step 8 by SPEC-136, immediately before this tap).
bash lib/gate/quiz-gate.sh tap <rid> --files "<changed files>" --impl-notes docs/implementation-notes/<slug>.md --pr-kind gate "<what changed>"
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.
- 4d ago First seen · 81 lines · 65 tokens per session scan A e2eb6df92217
quiz-gate is a command published in the GitHub repository dwarvesf/dwarves-kit (11 stars, last pushed today), licensed MIT. It adds 65 tokens to every session and 1,270 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: Onboard
Guided onboarding - walk through a complete OpenSpec workflow cycle with narration.
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).