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_sprints_from_milestonegit 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_sprints_from_milestone)<a href="https://agentmods.dev/commands/helmi/claude-simone/create_sprints_from_milestone"><img src="https://agentmods.dev/badge/commands/helmi/claude-simone/create_sprints_from_milestone.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.1 | $0.00000 | $0.01068 |
| Opus 5 | $0.00000 | $0.00534 |
| Sonnet 5 | $0.00000 | $0.00214 |
| Haiku 4.5 | $0.00000 | $0.00107 |
Grade A, and why
create_sprints_from_milestone 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 6d 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_sprints_from_milestone — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Sprints from a given Milestone. Execute from Top to Bottom
Follow these instructions to sprint the scope of a Milestone into Sprints
Create a TODO with EXACTLY these 8 items
- Analyze current milestone state
- Assess completed work vs milestone requirements
- Identify remaining work and dependencies
- Design logical sprint boundaries
- Create sprint directories and meta files
- Update PROJECT_MANIFEST with sprint roadmap
- Validate sprint coherence and dependencies
- Report milestone plan
1 · Analyze current milestone state
CRITICAL: You are given additional Arguments: <$ARGUMENTS>
USE PARALLEL SUBAGENTS to do these tasks:
- Parse arguments for milestone ID (defaults to current milestone from PROJECT_MANIFEST)
- Read
.simone/00_PROJECT_MANIFEST.mdto understand current progress - Scan
.simone/03_SPRINTS/to identify existing sprints for the target milestone - For each existing sprint, read its sprint meta file to determine status from YAML frontmatter
- Analyze the Tasks in Sprints to understand that work that has been done (from Subtasks)
2 · Assess completed work vs milestone requirements
- Read milestone meta file from
.simone/02_REQUIREMENTS/$MILESTONE_ID/ - CRITICAL: Follow and read ALL linked documents in the milestone meta:
- Product Requirements (PRD.md)
- Database Specifications (SPECS_DB.md)
- API Specifications (SPECS_API.md)
- Tool Specifications (SPECS_TOOLS.md)
- Any other linked specifications
- Study the milestone's Definition of Done (DoD) carefully and think deeply about what each DoD criterion actually requires in terms of specific deliverables
- For each existing sprint, analyze what deliverables have been completed by reading sprint meta and task files
- Think more carefully about the gap analysis: map each completed deliverable against specific DoD requirements and identify what's genuinely missing vs what might already be covered
- Create clear picture: "What's done vs what's required for milestone completion" with specific justification for each gap identified
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.
- 6d ago First seen · 122 lines · 0 tokens per session scan A 2a293c924aae
create_sprints_from_milestone is a command published in the GitHub repository Helmi/claude-simone (557 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,068 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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.