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/attilaszasz/sdd-pilotWrote 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/attilaszasz/sdd-pilot/_story-verifier)<a href="https://agentmods.dev/agents/attilaszasz/sdd-pilot/_story-verifier"><img src="https://agentmods.dev/badge/agents/attilaszasz/sdd-pilot/_story-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/attilaszasz/sdd-pilot/_story-verifier"><img src="https://agentmods.dev/badge/agents/attilaszasz/sdd-pilot/_story-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.00033 | $0.01188 |
| Opus 5 | $0.00016 | $0.00594 |
| Sonnet 5 | $0.00007 | $0.00238 |
| Haiku 4.5 | $0.00003 | $0.00119 |
Grade A, and why
StoryVerifier 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 12d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task
Trace prioritized work items from the spec against the implemented codebase.
Inputs
spec.md, plan.md, tasks.md, and the target project source code.
Execution Rules
Map "Given/When/Then" scenarios to actual code logic, tests, or UI components. Return explicit gaps where functionality is missing or partially implemented.
Output Format
A compact verification report containing PASSED, PARTIAL, and FAILED work items with specific missing criteria. When priorityChecks is provided, include ### Implementation Review Findings with every original finding, its RESOLVED | UNRESOLVED status, and its evidence-confirmed bugTargets array.
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.
- 12d ago First seen · 72 lines · 33 tokens per session scan A 1f6ffa2bb2db
StoryVerifier is an agent published in the GitHub repository attilaszasz/sdd-pilot (96 stars, last pushed 7d ago), licensed MIT. It adds 33 tokens to every session and 1,188 once invoked, about $0.0002 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 agents, from other repositories
task-verifier
Verifies a completed task against its spec acceptance criteria. Run after each worker subagent completes a task. Read-only -- cannot modify the codebase.
code-reviewer
Focused code reviewer. Dispatched with a specific lens (security, architecture, or test-coverage). Read-only. Used by /review-team for parallel review.
audit-scanner
Shared read-only Tier-2 evidence scanner for audit-loop instances (doc-drift, topology-drift, ci-drift, backlog-reconcile, web-drift, repo-hygiene, future ones). Dispatched by an audit skill with a target set + a contract + an evidence-class instruction; returns per-item findings with quoted evidence and severity in…
slop-stripper
Behavior-preserving AI-slop strip pass. Given a base ref, scans the branch diff and applies surgical edits that strip AI-generated smell (redundant comments, over-defensive handling, unnecessary casts, flattenable nesting, patterns inconsistent with the file) before merge. Never changes behavior unless fixing a real…
performance-reviewer
Reviews a diff through the PERFORMANCE lens only (hot paths, N+1, allocations, caching, latency, complexity). Read-only. Dispatched by /kit:review-team as the performance domain lens when the diff touches performance-sensitive code.
responding-to-review
Responds to code review feedback with technical rigor, not performative agreement. Verifies before implementing. Pushes back when reviewer is wrong. Read-only by design (proposes fixes; the user decides whether to apply).