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 commands/albertnahas/teamclaude/sprintgit 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/commands/albertnahas/teamclaude/sprint)<a href="https://agentmods.dev/commands/albertnahas/teamclaude/sprint"><img src="https://agentmods.dev/badge/commands/albertnahas/teamclaude/sprint.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.00016 | $0.02505 |
| Opus 5 | $0.00008 | $0.01252 |
| Sonnet 5 | $0.00003 | $0.00501 |
| Haiku 4.5 | $0.00002 | $0.00250 |
Grade A, and why
sprint 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 — 310 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint: Autonomous Development with Visualization
You are orchestrating an autonomous sprint. The mode depends on whether input was provided.
If $ARGUMENTS.input is provided → follow Manual Mode below (you parse the roadmap, create tasks, 2-agent sprint)
If no arguments → follow Autonomous Mode below (PM agent analyzes codebase, creates tasks, continuous 3-agent cycles)
Step 0: Detect Project Context
Before starting the sprint, detect the project's tooling so agents use the correct commands.
0a. Check for .sprint.yml
Read .sprint.yml in the project root (if it exists). This provides explicit configuration:
verification:
type_check: "pnpm type-check"
test: "pnpm test --run"
If .sprint.yml exists, use its values and skip auto-detection.
0b. Auto-detect Package Manager
Check which lockfile exists in the project root:
pnpm-lock.yaml→ pnpmyarn.lock→ yarnpackage-lock.json→ npmbun.lockborbun.lock→ bun- None found → no package manager detected
0c. Auto-detect Commands
Read package.json scripts (if it exists):
- If
scripts.type-checkexists → type-check command is{pm} type-check - If
scripts.typecheckexists → type-check command is{pm} typecheck - If neither → no type-check command (agents skip it)
- If
scripts.testexists → test command is{pm} test --run - If neither → no test command (agents skip it)
For non-JS projects (no package.json):
- Check for
Makefile→make test,make check - Check for
Cargo.toml→cargo check,cargo test - Check for
go.mod→go vet ./...,go test ./... - Check for
pyproject.tomlorsetup.py→pytest
0d. Build Context String
Compose a context string to inject into agent spawn prompts:
The project uses {pm}. Type-check: `{type_check_cmd}`. Test: `{test_cmd}`.
If a command is unavailable, note it: "No type-check command available — skip type-check verification."
Manual Mode
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 · 310 lines · 16 tokens per session scan A 29ce08357d83
sprint is a command published in the GitHub repository albertnahas/teamclaude (13 stars, last pushed 4mo ago), licensed MIT. It adds 16 tokens to every session and 2,505 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-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.