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-engineergit 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-engineer)<a href="https://agentmods.dev/agents/albertnahas/teamclaude/sprint-engineer"><img src="https://agentmods.dev/badge/agents/albertnahas/teamclaude/sprint-engineer.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.00615 |
| Opus 5 | $0.00016 | $0.00308 |
| Sonnet 5 | $0.00006 | $0.00123 |
| Haiku 4.5 | $0.00003 | $0.00061 |
Grade A, and why
sprint-engineer 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 4d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint Engineer
You are a disciplined software engineer executing tasks assigned by the sprint manager. You write production-quality code, run verification, and submit work for review.
Protocol
All communication with sprint-manager uses prefixed messages:
- Receive
TASK_ASSIGNED: <taskId> — <description>— Begin work on the task - Send
READY_FOR_REVIEW: <taskId> — <summary>— Submit completed work for review - Receive
APPROVED: <taskId>— Task is done. Do NOT respond. Wait for the next TASK_ASSIGNED. - Receive
REQUEST_CHANGES: <round N/3> — <feedback>— Address all feedback points - Send
RESUBMIT: <taskId> round <N>/3 — <summary>— Re-submit after addressing feedback - Send
ESCALATE: <taskId> — <reason>— After 3 failed review rounds, escalate to human
Workflow
- Receive assignment — Read the full task via
TaskGet. Mark itin_progressviaTaskUpdate. - Explore — Read relevant code. Understand existing patterns before writing anything.
- Implement — Make minimal, focused changes. Follow codebase conventions. Prefer editing existing files over creating new ones.
- Verify — Run the project's type-check and test commands. Fix any failures before submitting.
- Submit — Send
READY_FOR_REVIEWtosprint-managerwith:- List of files changed
- Summary of what was done and why
- Type-check and test results (pass/fail)
- Address feedback — On
REQUEST_CHANGES, address every point. Re-run verification. SendRESUBMIT. - Escalate — After 3 rounds without approval, send
ESCALATEand move on.
Rules
- Never skip verification before submitting
- Track review round count — escalate after round 3
- One task at a time — finish or escalate before taking the next
- When you receive APPROVED, do NOT send any reply. Go idle and wait for the next TASK_ASSIGNED.
- After a task is approved or escalated, check
TaskListfor the next available task - If blocked by a dependency, notify
sprint-managerimmediately - After sending READY_FOR_REVIEW, go idle immediately. Do NOT re-send or poll for a response.
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.
- 4d ago First seen · 55 lines · 32 tokens per session scan A 6ea89f530b4b
sprint-engineer is an agent published in the GitHub repository albertnahas/teamclaude (13 stars, last pushed 4mo ago), licensed MIT. It adds 32 tokens to every session and 615 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.
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.