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/yezannnnn/agentgroup/plan_milestonegit clone --depth 1 https://github.com/yezannnnn/agentGroupWrote 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/yezannnnn/agentgroup/plan_milestone)<a href="https://agentmods.dev/commands/yezannnnn/agentgroup/plan_milestone"><img src="https://agentmods.dev/badge/commands/yezannnnn/agentgroup/plan_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.01477 |
| Opus 5 | $0.00000 | $0.00739 |
| Sonnet 5 | $0.00000 | $0.00295 |
| Haiku 4.5 | $0.00000 | $0.00148 |
Grade A, and why
plan_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.
This is a copy
100% identical to plan_milestone — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan and Create New Milestone - Execute from Top to Bottom
Creates a new milestone with proper structure, documentation, and project integration through an interactive, adaptive process.
Create a TODO with EXACTLY these 8 items
- Parse arguments and analyze project context
- Interactive milestone scoping and definition
- Determine milestone structure and naming
- Create milestone directory and meta file
- Guide supporting documentation creation
- Update project manifest with milestone
- Validate milestone coherence and alignment
- Report milestone creation and next steps
1 · Parse arguments and analyze project context
CRITICAL: You are given additional Arguments: <$ARGUMENTS>
USE PARALLEL SUBAGENTS to do these tasks:
- Parse arguments for suggested milestone name/focus (defaults to interactive creation)
- Read
.simone/00_PROJECT_MANIFEST.mdto understand current project state - Scan
.simone/02_REQUIREMENTS/to identify existing milestones and numbering - Read
.simone/01_PROJECT_DOCS/ARCHITECTURE.mdto understand project scope - Check latest project review in
.simone/10_STATE_OF_PROJECT/for current status - IMPORTANT: Understand project phase and what logical next milestone should be
2 · Interactive milestone scoping and definition
Conversational milestone definition:
If arguments provided:
- "I see you want to create a milestone for: [arguments]"
- "Let me understand the scope better..."
If no arguments:
- "Let's define your next milestone based on the current project state"
- "I see you're currently on [current milestone] - what should we focus on next?"
Interactive questions (adapt based on context):
- "What's the main goal of this milestone?"
- "What key deliverables should be completed?"
- "Are there any specific technical challenges or requirements?"
- "How does this milestone advance the project toward its long-term vision?"
- "What would 'done' look like for this milestone?"
Keep conversational and adaptive - don't interrogate, just gather what's needed
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 · 190 lines · 0 tokens per session scan A 20152c888312
plan_milestone is a command published in the GitHub repository yezannnnn/agentGroup (149 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,477 tokens. A static security scan graded it A with 0 findings. It is 100% identical to plan_milestone, differing in 0 lines, and is treated as a copy.
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.