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/helmi/claude-simone/create_sprint_tasksgit clone --depth 1 https://github.com/Helmi/claude-simoneWrote 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/helmi/claude-simone/create_sprint_tasks)<a href="https://agentmods.dev/commands/helmi/claude-simone/create_sprint_tasks"><img src="https://agentmods.dev/badge/commands/helmi/claude-simone/create_sprint_tasks.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.00000 | $0.01574 |
| Opus 5 | $0.00000 | $0.00787 |
| Sonnet 5 | $0.00000 | $0.00315 |
| Haiku 4.5 | $0.00000 | $0.00157 |
Grade A, and why
create_sprint_tasks 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 5d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- create_sprint_tasks — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Tasks for Sprint - Execute top to bottom
Create detailed tasks for an existing sprint with integrated implementation guidance.
Create a TODO with EXACTLY these 8 Items
- Identify target sprint and verify it exists
- Load sprint context and related documentation
- Check for existing ADRs and technical guidance
- Analyze sprint deliverables for task breakdown
- Create individual task files with implementation guidance
- Link ADRs to relevant tasks
- Update sprint meta with task references
- Check quality of your work
Follow step by step and adhere closely to the following instructions for each step.
DETAILS on every TODO item
1. Identify target sprint and verify it exists
Check: <$ARGUMENTS>
REQUIRED: Sprint ID must be provided (e.g., S02). If empty, ask user to specify which sprint to detail.
- VERIFY sprint directory exists in
.simone/03_SPRINTS/ - CHECK sprint meta file exists (e.g.,
S02_sprint_meta.md) - VERIFY sprint status is not already "completed"
- If tasks already exist, ask user if they want to recreate them or any other guidance
2. Load sprint context and related documentation
Use PARALLEL SUBAGENTS to READ and UNDERSTAND the project's context:
- READ
.simone/00_PROJECT_MANIFEST.mdfor project context - READ sprint meta file completely to understand goals and deliverables
- READ parent milestone requirements from
.simone/02_REQUIREMENTS/ - READ
.simone/01_PROJECT_DOCS/ARCHITECTURE.mdfor technical context and decisions
IMPORTANT: Sprint tasks must align with documented sprint goals, not expand scope.
3. Check for existing ADRs and technical guidance
USE PARALLEL SUBAGENTS to execute these commands:
- SEARCH
.simone/05_ARCHITECTURE_DECISIONS/for ADRs matching sprint ID (e.g.,ADR*_S02_*.md) - READ all found ADRs to understand technical decisions
- CHECK sprint meta for ADR references section
- NOTE which technical decisions will affect task implementation
- BUILD RELATIONSHIP in task and subtasks and make clear what to implement
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.
- 5d ago First seen · 189 lines · 0 tokens per session scan A 14e3f061de2c
create_sprint_tasks is a command published in the GitHub repository Helmi/claude-simone (558 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,574 tokens. 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
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.