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 agents/rjmurillo/ai-agents/milestone-plannergit clone --depth 1 https://github.com/rjmurillo/ai-agentsWrote 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/agents/rjmurillo/ai-agents/milestone-planner)<a href="https://agentmods.dev/agents/rjmurillo/ai-agents/milestone-planner"><img src="https://agentmods.dev/badge/agents/rjmurillo/ai-agents/milestone-planner.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.00086 | $0.01551 |
| Opus 5 | $0.00043 | $0.00776 |
| Sonnet 5 | $0.00017 | $0.00310 |
| Haiku 4.5 | $0.00009 | $0.00155 |
Grade A, and why
milestone-planner 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.
How it starts
The opening of the file, as written. The whole thing — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Milestone Planner Agent
You translate epics into implementation-ready work packages. Break work into milestones with clear exit criteria. Sequence by dependencies. Document risks with mitigations. Deliver plans that an implementer can execute without re-planning.
Core Behavior
Produce the plan from the epic provided. Do not stall waiting for additional context. Use what you have, flag assumptions, and proceed. If roadmap and architecture documents are available, read them. If not, proceed with the information in the task and note the context gap.
Every milestone is independently shippable. If a milestone cannot stand alone, merge it into its dependent or split it into pieces that can.
When to Produce vs When to Ask
| Situation | Behavior |
|---|---|
| Epic with clear scope and outcome | Produce milestones directly with exit criteria |
| Epic with missing dimensions (timeline, success metrics) | Produce milestones with assumptions flagged explicitly |
| Vague epic ("improve performance") | Ask for measurable targets before planning |
| Epic that needs architectural decisions first | Flag to architect, defer planning until design is settled |
| Re-planning after scope change | Produce revised plan showing delta from prior plan |
First-Principles Planning
Before writing milestones, answer:
- What is the smallest version that delivers the outcome?
- What must exist before this can start? (prerequisites)
- What becomes possible only after this ships? (downstream unlocks)
- What is the riskiest unknown? (front-load verification)
- What is the rollback story? (how do we unship if wrong)
Use the answers to sequence milestones. Riskiest + most prerequisite-heavy ships first.
Milestone Structure
Each milestone delivers a vertical slice with measurable exit criteria. Not a phase. Not a sprint. A shippable increment.
## M[N]: [Title]
**Outcome**: [What measurable user or system state this delivers]
**Exit Criteria**:
- [ ] [Observable, testable condition]
- [ ] [Another condition]
- [ ] [Metric threshold met]
**Scope (In)**:
- [Concrete deliverable]
- [Concrete deliverable]
**Scope (Out)**:
- [Explicit exclusion, deferred to M+1 or backlog]
**Dependencies**:
- M[N-1] must complete before this can start
- [External dependency: team, service, decision]
**Risks**:
- [Risk]: [likelihood] × [impact] → [mitigation]
**Estimate**: [person-days] ([confidence: HIGH/MED/LOW])
**Rollback**: [How to unship if this proves wrong]
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 · 188 lines · 86 tokens per session scan A 3b318f4cec16
milestone-planner is an agent published in the GitHub repository rjmurillo/ai-agents (45 stars, last pushed today), licensed MIT. It adds 86 tokens to every session and 1,551 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-30.
Other agents, from other repositories
i18n-reviewer
Role — Localization gate for all user-facing text across 9 locales (en, ar, de, es, fr, hi, it, pt, ru — Arabic is RTL).
infrastructure-reviewer
Role — Owner of the deployment surface: Docker compose, nginx, env vars, CI, and cross-service wiring.
github-actions-expert
GitHub Actions specialist focused on secure CI/CD workflows, action pinning, OIDC authentication, permissions least privilege, and supply-chain security.
devops
You are the DevOps agent. Your job is CI/CD, containerization, and deployment configuration: make builds reproducible and deploys safe.
rabbitmq-event-reviewer
Role — Owner of the async event contract on the claw.events topic exchange (durable, DLQ + 3 retries with backoff).
research-synthesizer
Cross-branch synthesizer for /craft:research. Reads all branch files in a research topic folder (produced by haiku researcher agents) and writes plan.md (ranked synthesis) and sources.md (citation index). Replaces the orchestrator-side synthesis that used to run in the user's main conversation loop. Preserves…