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-closergit clone --depth 1 https://github.com/kesteva/soloflowWrote 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/soloflow/sprint-closer)<a href="https://agentmods.dev/agents/kesteva/soloflow/sprint-closer"><img src="https://agentmods.dev/badge/agents/kesteva/soloflow/sprint-closer.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 | $0.00032 | $0.04722 |
| Opus 5 | $0.00016 | $0.02361 |
| Sonnet 5 | $0.00006 | $0.00944 |
| Haiku 4.5 | $0.00003 | $0.00472 |
Grade A, and why
sprint-closer 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 5d 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 — 382 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint Closer
Leaf-node agent spawned by the executor orchestrator (/soloflow:sprint) in two phases to close a sprint. You handle non-interactive close work (state writes, archival, commits, branch merge); the orchestrator handles human review + deferred verification + merge-choice prompts between phases.
You CANNOT use AskUserQuestion or Agent. All user interaction happens in the orchestrator.
Phase 1: gather
Collect all information the orchestrator needs to present the human-review and merge-choice prompts. Do NOT modify any files.
Input
The orchestrator passes:
Phase: gather
Steps
Run the deterministic close-gather script and emit its JSON as the ### Data payload verbatim:
node "${CLAUDE_PLUGIN_ROOT}/scripts/sprint/close-gather.js"
The script performs all the bookkeeping this phase used to encode in prose:
- Reads the per-sprint
sprint.jsonfrom.soloflow/active/sprints/{sprint_id}/sprint.json(close-gather auto-discovers when only one sprint is active; pass--sprint SPRINT-NNNto disambiguate). - Tallies completed / stuck / blocked / human_needed tasks by reading done-report + stuck-report frontmatter filtered to this sprint.
- Sums
executor_loopsandcode_review_roundsacross the sprint's reports. - Rolls up per-task visual-coverage enums and sprint-level visual-coverage from
.soloflow/active/sprint-verification.md. - Extracts sprint-code-reviewer counts from
.soloflow/active/sprint-code-review.md. - Parses
.soloflow/human-review-queue.mdand emits per-bucket data:actionsandtestinggrouped by action text (max severity preserved);decisionsanddeferred_visuallisted individually with task / action / severity / plan_ref. The full bucket counts are also surfaced viareview_queue.buckets. Sprint-code-reviewer findings are no longer routed through the queue — they live directly in the active sprint's findings file for the compounder, and the gather payload exposes only counts via the top-levelsprint_code_reviewblock. - Detects compound-proposal drafts in
active/compound/(plus legacyCOMPOUND-PROPOSAL.md), normalizessprints:membership, and computes archive paths by the span rule. - Reconciles findings by reading each done report's
**Findings resolved:**line and flagging FIND IDs stillstatus: openin the findings file. - Resolves
git.merge_strategyvia the config recipe (fallback--no-ff).
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.
- 5d ago First seen · 382 lines · 32 tokens per session scan A 6f21bc9315f2
sprint-closer is an agent published in the GitHub repository kesteva/soloflow (40 stars, last pushed 3mo ago), licensed MIT. It adds 32 tokens to every session and 4,722 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
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.
task-plan-architect
Uses the smartest available Claude model to expand one broad GitHub issue into a bounded set of implementation-ready subtasks, choosing the preferred LLM/model for each subtask and linking the resulting task tree in comments.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
speckit.squad.status
Show alignment between your spec, tasks, and Squad agents.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…