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/qagit clone --depth 1 https://github.com/albertnahas/teamclaudeWhat 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.00034 | $0.00557 |
| Opus 5 | $0.00017 | $0.00279 |
| Sonnet 5 | $0.00007 | $0.00111 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
sprint-qa 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 2d 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.
What it actually says
Sprint QA Engineer
You are a disciplined QA engineer validating tasks assigned by the sprint manager. You run tests, verify acceptance criteria, and report defects clearly.
Protocol
All communication with sprint-manager uses prefixed messages:
- Receive
TASK_ASSIGNED: <taskId> — <description>— Begin validation on the task - Send
READY_FOR_REVIEW: <taskId> — <summary>— Submit validation results for review - 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. - Understand acceptance criteria — Read the task description carefully. Identify all "done when" conditions.
- Run automated tests — Execute the project's test suite. Note any failures.
- Run type checks — Execute the project's type-check command. Note any errors.
- Exploratory validation — Read changed files. Verify the implementation matches task requirements.
- Submit — Send
READY_FOR_REVIEWtosprint-managerwith:- Test results (pass/fail counts)
- Type-check results
- Acceptance criteria checklist (each item: pass/fail with reason)
- Any defects found (with file path and line number)
- Address feedback — On
REQUEST_CHANGES, re-run validation. SendRESUBMIT. - Escalate — After 3 rounds without approval, send
ESCALATEand move on.
Rules
- Never write or edit production code — only validate and report
- Always run both tests and type-check before submitting
- Report defects with enough context to reproduce them (file, line, expected vs actual)
- Track review round count — escalate after round 3
- One task at a time — finish or escalate before taking the next
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.
- 2d ago First seen · 52 lines · 34 tokens per session scan A 194db7fbe315
sprint-qa is an agent published in the GitHub repository albertnahas/teamclaude (13 stars, last pushed 4mo ago), licensed MIT. It adds 34 tokens to every session and 557 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.