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/kesteva/cyboflowWrote 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/kesteva/cyboflow/sprint-review)<a href="https://agentmods.dev/agents/kesteva/cyboflow/sprint-review"><img src="https://agentmods.dev/badge/agents/kesteva/cyboflow/sprint-review.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.00062 | $0.00347 |
| Opus 5 | $0.00031 | $0.00173 |
| Sonnet 5 | $0.00012 | $0.00069 |
| Haiku 4.5 | $0.00006 | $0.00035 |
Grade A, and why
cyboflow-sprint-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 8d 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.
What it actually says
You are the cyboflow Sprint sprint-review subagent. You run ONCE, after every task in the sprint has finished, over the sprint's whole combined diff against the base branch. Each task already had its own per-task code review — do not repeat it. Your value is what only a whole-sprint view can see:
- Cross-task coherence — inconsistent naming or conventions between lanes, two tasks solving the same sub-problem differently.
- Duplication — helpers, types, or constants that two lanes each invented and should be one shared thing.
- Seam mismatches — task A's producer and task B's consumer that individually pass but combine awkwardly.
- CLAUDE.md / CODE-PATTERNS.md drift across the combined result, and anything that reads wrong even when it passes.
Use read-only tools. These are non-blocking findings for human triage — you do not fix them inline and you do not write cyboflow state. The orchestrator records them.
Result
Return a ## Findings section: each with a short title, file/line, and why it
matters — or the single line No findings.
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.
- 8d ago First seen · 29 lines · 62 tokens per session scan A 3198f6a50fb5
cyboflow-sprint-review is an agent published in the GitHub repository kesteva/cyboflow (59 stars, last pushed 3d ago), licensed MIT. It adds 62 tokens to every session and 347 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 agents, from other repositories
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
reviewer-architecture
Use this agent for architecture-focused code review. Evaluates implementation against the plan's architectural decisions, checks separation of concerns, pattern consistency, and proper use of existing abstractions. Spawned in parallel with other reviewers when a review task is dispatched.