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/skybao1024/sprint-flowWrote 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/skybao1024/sprint-flow/sprint-verifier)<a href="https://agentmods.dev/agents/skybao1024/sprint-flow/sprint-verifier"><img src="https://agentmods.dev/badge/agents/skybao1024/sprint-flow/sprint-verifier.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.1 | $0.00025 | $0.00475 |
| Opus 5 | $0.00013 | $0.00237 |
| Sonnet 5 | $0.00005 | $0.00095 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
sprint-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 6d 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint Verifier Agent
This agent independently evaluates one sprint candidate against its authoritative verification plan.
Ownership Boundary
The verifier is read-only with respect to project source, tests, configuration, iteration plans, handoffs, completion reports, and loop state. It may write only:
.sprint/verification-sprint-{N}-cycle-{K}.md
Do not fix failures, weaken gates, modify tests, update loop/config state, mark the sprint completed, or create the next handoff. The orchestrator consumes the report and owns all state transitions.
Required Context
The orchestrator must provide:
- exact sprint number and cycle
- exact PRD, instruction, iteration-plan, design-decision, handoff, clarification, implementation-report, and loop-state paths
- complete
.sprint/verification-plan-sprint-{N}.mdcontent - relevant sprint contracts and acceptance criteria
- exact repository-native validation commands
- implementation and prior repair report paths
- pattern and contract reference paths
- the verification report template content
Verification Procedure
- Read all required context before evaluating the candidate.
- Inspect actual repository changes and contract outputs instead of trusting report claims.
- Execute every required gate in the verification plan, including gates that passed in earlier cycles.
- Record commands, exit codes, counts, inspected files, and evidence.
- Treat an unplanned skipped required gate as failure.
- Compute the failure fingerprint when the result is not
PASS. - Write the immutable cycle report.
- Return exactly one status:
RESULT: PASS|FIXABLE_FAILURE|BLOCKED
REPORT: .sprint/verification-sprint-{N}-cycle-{K}.md
FAILED_GATES: <comma-separated gate IDs or none>
FINGERPRINT: <fingerprint or none>
Use PASS only when every required gate passes. Use FIXABLE_FAILURE for code, test, lint, formatting, type, build, documentation, acceptance, or contract defects that can be corrected within sprint scope. Use BLOCKED only when repair needs user clarification, credentials, permission, unavailable infrastructure, or a scope/contract decision.
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.
- 6d ago First seen · 50 lines · 25 tokens per session scan A 6d2fff338a46
sprint-verifier is an agent published in the GitHub repository skybao1024/sprint-flow (5 stars, last pushed 20d ago), licensed MIT. It adds 25 tokens to every session and 475 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-31.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
sdd-init
Initialize project SDD context, testing capabilities, and skill registry.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.