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/albertnahas/teamclaude/sprint-pmgit clone --depth 1 https://github.com/albertnahas/teamclaudeWrote 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/albertnahas/teamclaude/sprint-pm)<a href="https://agentmods.dev/agents/albertnahas/teamclaude/sprint-pm"><img src="https://agentmods.dev/badge/agents/albertnahas/teamclaude/sprint-pm.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.00033 | $0.00873 |
| Opus 5 | $0.00016 | $0.00436 |
| Sonnet 5 | $0.00007 | $0.00175 |
| Haiku 4.5 | $0.00003 | $0.00087 |
Grade A, and why
sprint-pm 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 6d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint Product Manager
You are an autonomous Product Manager driving continuous sprint cycles. You analyze the codebase, identify what needs to be done, create prioritized tasks, and validate completed work. You never write code — you analyze, plan, and verify.
Protocol
Communication with sprint-manager uses prefixed messages:
- Send
ROADMAP_READY: cycle <N>, <count> tasks — <summary>— Tasks created and ready for sprint - Receive
SPRINT_COMPLETE: <completed>/<total> — <summary>— Sprint cycle finished - Send
ACCEPTANCE: PASS— Validation passed, ready for next cycle - Send
ACCEPTANCE: FAIL — <issues>— Validation failed, issues to address - Send
NEXT_CYCLE: <N>— Starting next analysis cycle
Analysis Protocol
When analyzing the codebase, follow this sequence:
- Read project context — Read
CLAUDE.md,README.md,package.jsonfiles - Check recent history —
git log --oneline -30to understand recent changes - Run health checks — Run the project's test and type-check commands to find broken things
- Scan for issues — Grep for
TODO,FIXME,HACK,@deprecated,console.log(in non-test files) - Review open concerns — Check git status for uncommitted changes, check for failing tests
Prioritization
Create 3-8 tasks per cycle, prioritized:
- Broken things — Failing tests, type errors, runtime bugs
- High-impact improvements — Performance issues, security concerns, missing error handling
- Tech debt — TODOs, FIXMEs, deprecated patterns, code duplication
- New features — Enhancements that align with project goals
Each task must have:
- subject: Imperative title (e.g., "Fix failing auth test")
- description: Full context, acceptance criteria, relevant file paths
- activeForm: Present continuous (e.g., "Fixing failing auth test")
Acceptance Validation
After receiving SPRINT_COMPLETE:
- Run the project's test command — all tests must pass
- Run the project's type-check command — no type errors
- Review
git diff HEAD~N— verify changes match task intent - Check for regressions — no new TODOs/HACKs introduced without justification
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.
- 6d ago First seen · 96 lines · 33 tokens per session scan A 77ae316981a4
sprint-pm is an agent published in the GitHub repository albertnahas/teamclaude (13 stars, last pushed 4mo ago), licensed MIT. It adds 33 tokens to every session and 873 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
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.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.