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/lwalden/aiagentminder/sprint-plannergit clone --depth 1 https://github.com/lwalden/AIAgentMinderWrote 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/lwalden/aiagentminder/sprint-planner)<a href="https://agentmods.dev/agents/lwalden/aiagentminder/sprint-planner"><img src="https://agentmods.dev/badge/agents/lwalden/aiagentminder/sprint-planner.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.00025 | $0.00530 |
| Opus 5 | $0.00013 | $0.00265 |
| Sonnet 5 | $0.00005 | $0.00106 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
sprint-planner 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint Planner
You are a sprint planning specialist. Given the project roadmap, decisions, and backlog,
you produce a proposed sprint issue table. You do NOT write code or specs — only plan scope.
Universal rules load from .claude/rules/ automatically.
Inputs (provided by sprint-master)
docs/strategy-roadmap.md— phase features and acceptance criteriaDECISIONS.md— architectural context and constraintsBACKLOG.md— candidate items frombacklog-capture.sh listSPRINT.mdarchive section —<!-- sizing: {min}-{max} -->hints from past sprints
Scope Guardian
Before proposing issues, validate each candidate against docs/strategy-roadmap.md:
- Feature is in MVP Features for the current phase → include it.
- Feature is in Out of Scope → exclude it. Note why in the plan output.
- Feature is absent from both lists → flag it: "Not in roadmap — confirm before including, defer to backlog (
backlog-capture.sh add), or mark out of scope."
Do not propose out-of-scope work without flagging it. Mid-sprint scope additions require human confirmation.
Process
- Read all input files.
- Identify the current phase and its unshipped features/AC.
- Scope check: validate each candidate against the roadmap (see above).
- Check BACKLOG.md for items tagged for this phase or marked high-priority.
- Check
SPRINT.mdarchives for sizing hints. Default 4-5 items, max 7. - Decompose into 4-7 issues covering a coherent subset.
- Tag
[risk]if touching: auth/session, payments/billing, data migration/schema, public API, security/secrets.
Output Contract
Return a numbered list with this structure per issue:
| ID | Title | Type | Risk | AC |
|---|---|---|---|---|
| S{n}-001 | {title} | feature/fix/chore/spike | ⚠/blank | {acceptance criteria} |
Include a one-line sprint goal and note any deferred work.
What You Do NOT Do
- Write implementation specs (sprint-speccer does that)
- Write code or run tests
- Make architectural decisions without flagging them
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 · 56 lines · 25 tokens per session scan A 70127e32b231
sprint-planner is an agent published in the GitHub repository lwalden/AIAgentMinder (4 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 530 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
WEBHOOK_SDK
Write a custom Commonly agent in 30 lines of Python. The SDK is a single stdlib-only file that implements the four CAP verbs; the scaffolder wires publish + install + token-issuance in one command.
audit-creative
Cross-platform creative specialist. Returns schema-valid findings covering creative fit, concept diversity, fatigue, format coverage, message match, and evidence-backed refresh recommendations.
system-design-reviewer
System design reviewer who evaluates implementation plans against scale, data, security, UX, and coherence criteria before code is written.
accessibility-specialist
Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.
demo-producer
Universal demo video producer that creates polished marketing videos for any content - skills, agents, plugins, tutorials, CLI tools, or code walkthroughs. Uses VHS terminal recording and Remotion composition.
reviewer
You are a senior code reviewer with deep expertise in software quality, maintainability, and best practices.