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.
git clone --depth 1 https://github.com/SienkLogic/plan-build-runWrote 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/sienklogic/plan-build-run/milestone-summary)<a href="https://agentmods.dev/commands/sienklogic/plan-build-run/milestone-summary"><img src="https://agentmods.dev/badge/commands/sienklogic/plan-build-run/milestone-summary.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.00015 | $0.00043 |
| Opus 5 | $0.00008 | $0.00022 |
| Sonnet 5 | $0.00003 | $0.00009 |
| Haiku 4.5 | $0.00002 | $0.00004 |
Grade A, and why
milestone-summary 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.
What it actually says
This command is provided by the pbr:milestone-summary skill.
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 · 7 lines · 15 tokens per session scan A f5a7872c6203
milestone-summary is a command published in the GitHub repository SienkLogic/plan-build-run (17 stars, last pushed 5mo ago), licensed MIT. It adds 15 tokens to every session and 43 once invoked, about $0.0001 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 commands, from other repositories
feedback
Collect feedback and create GitHub issue (bug report, feature request).
todo
Backlog queue for Kanban Mode — add, list, or pick the next card.
planning
Planning semanal de equipo con revisión de RFCs, priorización, asignación por responsable/pareja/squad y seguimiento.
migrar
Planificar y ejecutar migración entre stacks tecnológicos o versiones mayores.
audit-trail
Generar y consultar el log de auditoría de decisiones asistidas por IA. Usa cuando el usuario dice "audit trail", "decision log", "log de decisiones", "AI decisions", "audit log", "追溯", "track decisions", "quien decidió qué", "decision history". Registra y consulta el log de decisiones tomadas durante la sesión.
comenzar
Iniciar tarea nueva SDD con complejidad auto-detectada (0-4). Usa cuando el usuario dice "quiero iniciar tarea", "empezar feature", "nueva historia", "comenzar desarrollo", "start a new task/feature/story", "iniciar un feature". Detecta si es tarea rápida (nivel 1), normal (nivel 2) o compleja (nivel 3-4) y adapta el…