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 skills/rbah31/claude-code-workflow/sprint-plannpx skills add rbah31/claude-code-workflow --skill sprint-plangit clone --depth 1 https://github.com/rbah31/claude-code-workflowWrote 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/skills/rbah31/claude-code-workflow/sprint-plan)<a href="https://agentmods.dev/skills/rbah31/claude-code-workflow/sprint-plan"><img src="https://agentmods.dev/badge/skills/rbah31/claude-code-workflow/sprint-plan.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.00075 | $0.00896 |
| Opus 5 | $0.00037 | $0.00448 |
| Sonnet 5 | $0.00015 | $0.00179 |
| Haiku 4.5 | $0.00007 | $0.00090 |
Grade A, and why
sprint-plan 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint Planning
You are running the sprint planning phase. Your job is to produce a clear, actionable plan that the build phase can execute autonomously.
Step 1 — Gather context
Read these files in order. If a file doesn't exist, skip it and note its absence.
tasks/backlog.md— what needs to be donetasks/lessons.md— what we've learned from past sprints- The most recent
tasks/sprints/sprint-*/retrospective.md— what worked and didn't last time
Step 2 — Determine sprint number
Look at existing tasks/sprints/sprint-* directories. The next sprint is N+1.
Create the directory: tasks/sprints/sprint-XX/
Step 3 — Read-only discipline
During planning, do NOT modify any project files except the plan.md
itself (which you write at Step 6). Do NOT activate Claude Code's
plan mode — in non-interactive claude -p sessions, plan mode
terminates via ExitPlanMode awaiting human approval, causing a
silent exit 0 with no output. Stay in normal mode and self-discipline:
read everything you need, but only write tasks/sprints/sprint-XX/plan.md
at the end.
Step 4 — Produce the plan
Use the architect subagent to analyze the codebase and propose a plan.
The plan must follow this structure:
# Sprint XX — [Theme or focus]
## Goal
[One sentence: what this sprint delivers]
## Type
[hotfix | normal | security] — determines which phases to run
## Tasks
### Task 1: [Name]
- **Description**: [What to do]
- **Acceptance criteria**: [How to verify it's done]
- **Files likely affected**: [List]
- **Complexity**: S / M / L
- **Dependencies**: [Other tasks or none]
### Task 2: [Name]
...
## Risks
- [Risk 1]: [Mitigation]
- [Risk 2]: [Mitigation]
## Alternatives considered
- [Alternative rejected and why]
## Assignment (duo mode)
- Engineer A: [Tasks]
- Engineer B: [Tasks]
Step 5 — Self-challenge
Before presenting the plan, play devil's advocate on your own work:
- Are there hidden dependencies between tasks?
- Is the scope realistic for one sprint?
- Are we over-engineering anything?
- Are we missing anything obvious from the backlog or lessons?
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 · 110 lines · 75 tokens per session scan A 0b7bb81ef100
sprint-plan is a skill published in the GitHub repository rbah31/claude-code-workflow (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 75 tokens to every session and 896 once invoked, about $0.0004 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 skills, from other repositories
agent-code-analyzer
Agent skill for code-analyzer - invoke with $agent-code-analyzer.
worker-integration
Worker-Agent integration for intelligent task dispatch and performance tracking.
agui-dotnet-sample-step
Add a GettingStarted sample Step (a Server/Client pair) to the AG-UI .NET SDK that demonstrates one protocol feature the way we want users to write it. USE FOR: adding a new samples/GettingStarted/StepNN Server+Client pair, wiring it into AGUI.slnx and the integration-test project, giving it a deterministic…
agui-dotnet-protobuf
Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…
cog-knowledge-consolidation
Build structured knowledge frameworks from scattered vault notes with source attribution.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…