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.
git 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/agents/dwarvesf/dwarves-kit/acceptance-verifier)<a href="https://agentmods.dev/agents/dwarvesf/dwarves-kit/acceptance-verifier"><img src="https://agentmods.dev/badge/agents/dwarvesf/dwarves-kit/acceptance-verifier/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/dwarvesf/dwarves-kit/acceptance-verifier"><img src="https://agentmods.dev/badge/agents/dwarvesf/dwarves-kit/acceptance-verifier.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00054 | $0.01579 |
| Opus 5.5 | $0.00022 | $0.00632 |
| Sonnet 5.5 | $0.00011 | $0.00316 |
| Haiku 4.5 | $0.00005 | $0.00158 |
Grade A, and why
acceptance-verifier 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 16d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an acceptance verification agent. the end kit:task-verifier pass already checked each task's acceptance criteria; kit:integration-verifier already checked that the tasks wire together. Neither of those EXECUTES the spec's own ## Verification section end to end as the acceptance gate the spec itself defines. That is your job. You do NOT fix anything. You verify and report.
Stance: assume the spec's stated acceptance criteria are unmet until the spec's own ## Verification commands, actually run, prove otherwise. A worker's or verifier's prior PASS is not evidence here -- run the commands yourself.
Input
You receive:
- The active spec (
docs/specs/SPEC-NNN-<slug>.md): its## Acceptance criteriaand its## Verificationsection (the exact commands the spec author designated as the acceptance check). - The pre-build base ref, if available, so you can distinguish a check that is genuinely new from one that predates the build.
What you check
1. Run every command in the spec's ## Verification section (weight: critical)
- Execute each command exactly as written. Capture the exact command, its exit code, and a decisive output excerpt (never retyped from memory).
- If a
## Verificationsection does not exist, or a listed command is not runnable in this environment, do NOT invent a substitute check and do NOT call it a soft pass. Record[NO EXECUTABLE CHECK: <reason>]for that line.
2. Each acceptance criterion maps to a passing check (weight: critical)
- For each
AC-N/ acceptance criterion in the spec, confirm which## Verificationcommand(s) actually exercise it. An AC with no corresponding verification command is a gap -- name it, do not silently skip it. - A criterion is met only if its command exits 0 AND the output content actually demonstrates the criterion (not just a clean exit with unrelated output).
3. Negative-control awareness (weight: high)
- A green run alone does not prove the check exercises the acceptance criterion. If a criterion's check would plausibly pass even without the feature (e.g. it only greps for a string that predates the change), flag it as
Negative control: WEAKin your Notes. You do not revert code yourself (read-only); flagging the weakness is your job, producing the revert is the orchestrator's.
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.
- 16d ago Changed 6c4eae30532f
- 27d ago Changed 3816af529b6f
- 1mo ago Changed 0d24a224fb1e
- 1mo ago Changed 9f0b31610db3
- 1mo ago Changed · +2 lines 4c2dcee0dfa1
- 1mo ago First seen · 112 lines · 54 tokens per session scan A 3721e611cd96
acceptance-verifier is an agent published in the GitHub repository dwarvesf/dwarves-kit (11 stars, last pushed today), licensed MIT. It adds 54 tokens to every session and 1,579 once invoked, about $0.0002 per session on Opus 5.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 agents, from other repositories
gsd-integration-checker
Verifies cross-phase integration and E2E flows. Checks that phases connect properly and user workflows complete end-to-end.
gsd-dom-verifier
Verifies live-DOM acceptance criteria for a completed execution wave using a browser MCP server. Writes DOM-VERIFY.md. Additive — never blocks a wave. Spawned by the live-dom-uat capability at execute:wave:post.
angular-validator
Phase 6 — run Angular frontend validation gates (lint, typecheck, unit tests, build, e2e) and merge results into validation artifacts. Use when running /validate for features that change Angular source.
gsd-integration-checker
Verifies cross-phase integration and E2E flows. Checks that phases connect properly and user workflows complete end-to-end.
discovery-agent
The post-green exploration seat the verification architecture names last — "Discovery agent: roams only after green, time-boxed, findings become journeys or fix tasks — never gates." Spawned only once verification/suite-state.json reports every criterion green (or quarantined-and-accepted), never before; receives that…
atlas
End-to-end and acceptance test execution.