Borrowing it
Nothing to install: this file belongs to MarcTorrent/sprint-orchestrator. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/MarcTorrent/sprint-orchestrator/main/.claude/commands/generate-sprint.mdgit clone --depth 1 https://github.com/MarcTorrent/sprint-orchestratorWrote 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/marctorrent/sprint-orchestrator/generate-sprint)<a href="https://agentmods.dev/commands/marctorrent/sprint-orchestrator/generate-sprint"><img src="https://agentmods.dev/badge/commands/marctorrent/sprint-orchestrator/generate-sprint/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/marctorrent/sprint-orchestrator/generate-sprint"><img src="https://agentmods.dev/badge/commands/marctorrent/sprint-orchestrator/generate-sprint.svg" alt="Reviewed on agentmods" width="80" 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.00072 | $0.02210 |
| Opus 5 | $0.00036 | $0.01105 |
| Sonnet 5 | $0.00014 | $0.00442 |
| Haiku 4.5 | $0.00007 | $0.00221 |
Grade A, and why
generate-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 10d 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 — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint Generator Command
Generate comprehensive sprint backlog files from your project documentation. This command intelligently extracts tasks, estimates effort, assigns agents to tasks, and splits work into manageable sprints. Important: This command does NOT define workstreams or group tasks into workstreams - that is exclusively the orchestrator's responsibility.
Step 1: Understand the Project Context
Before generating sprints, analyze the project to understand:
- Project Structure: Review codebase organization (frontend/backend, services, components)
- Existing Agents: Check if there are agent definitions in documentation or code comments
- Technology Stack: Understand languages, frameworks, and tools used
- Documentation Sources: Identify where tasks/features are documented
Key files to review:
README.md- Project overview and setupdocs/directory - Feature documentationCLAUDE.md- Project-specific context- Codebase structure - Understand architecture
- Previous sprint files (if any) - Understand patterns
Step 2: Extract All Tasks
Read through all project documentation and extract tasks. Look for:
- TODO comments in code
- Feature lists in markdown files
- Roadmap items
- Implementation plans
- Bug reports or issues
- Requirements documentation
Extract for each task:
- Description (what needs to be done)
- Source file/section (where it was found)
- Context (surrounding documentation)
Step 3: Estimate Story Points
For each extracted task, estimate story points using standard Fibonacci scale (1, 2, 3, 5, 8, 13, 21):
Estimation Guidelines:
- 1 SP: Trivial changes (typo fixes, simple config)
- 2 SP: Small features (single component, simple API endpoint)
- 3 SP: Medium features (multiple components, moderate complexity)
- 5 SP: Large features (significant refactoring, complex integrations)
- 8 SP: Very large features (major refactoring, new subsystems)
- 13+ SP: Epic-level work (should be broken down)
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.
- 10d ago First seen · 278 lines · 0 tokens per session scan A 61cb9baf1f8d
generate-sprint is a command published in the GitHub repository MarcTorrent/sprint-orchestrator (2 stars, last pushed 4mo ago), licensed MIT. It adds 72 tokens to every session and 2,210 once invoked, about $0.0004 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 commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.