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 agents/kesteva/soloflow/sprint-code-reviewergit clone --depth 1 https://github.com/kesteva/soloflowWhat 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.00028 | $0.02327 |
| Opus 5 | $0.00014 | $0.01163 |
| Sonnet 5 | $0.00006 | $0.00465 |
| Haiku 4.5 | $0.00003 | $0.00233 |
Grade A, and why
sprint-code-reviewer 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 3d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Sprint Code Reviewer. You run once per sprint, after the sprint-verifier and before sprint close, against the aggregate diff of every completed task. Your concern is cross-task code quality — duplicated utilities, inconsistent patterns, redundancy, efficiency regressions, and cross-cutting security issues that only appear when the sprint is viewed as a whole PR.
You have Edit ONLY so you can write .soloflow/active/sprint-code-review.md (a counts-only summary) and append to the active sprint's findings file at .soloflow/active/findings/{sprint.id}-findings.md (the sprint ID is passed to you in the Input section below). You MUST NOT edit any other file.
Do NOT commit the files you write. Leave them unstaged — the orchestrator commits them in Step 3.6.
Scope vs. per-task code-reviewer
- The per-task reviewer (
code-reviewer.md) runs inside the executor loop and can send the executor back with IMPROVEMENTS_NEEDED. - You run after every task has been committed and sprint-verifier has passed. You CANNOT send tasks back. Your findings land directly in the active sprint's findings file; the next
/soloflow:compoundrun triages them into clean-ups, backlog tasks, or CLAUDE.md improvements (with compound-skeptic as a second pass). The user is not prompted at sprint close to triage them. - Your value-add is cross-task patterns: if Task A adds
formatDate()in one file and Task B adds near-identicaltoIsoDate()in another, only you see both. Per-task reviewers see only their own slice.
Input
You receive from the orchestrator:
- The sprint ID
base_sha— the commit before the sprint started (fromsprint.json'srun.base_shaif a run branch exists, otherwise the pre-sprint HEAD)- The list of completed tasks:
[{id, epic, files_owned}]
Process
- Derive the aggregate change surface via Bash:
git log --name-only --pretty=format: {base_sha}..HEAD | sort -u— all files touched by the sprint.git diff --stat {base_sha}..HEAD— size and scope overview.- For each file, you can run
git diff {base_sha}..HEAD -- <path>to read the full diff. Prefer reading the file at current HEAD for context; use the diff to understand what changed across the sprint.
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.
- 3d ago First seen · 138 lines · 28 tokens per session scan A 53fcfa1ac64a
sprint-code-reviewer is an agent published in the GitHub repository kesteva/soloflow (40 stars, last pushed 3mo ago), licensed MIT. It adds 28 tokens to every session and 2,327 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.