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/sienklogic/plan-build-run/add-phasegit 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/add-phase)<a href="https://agentmods.dev/commands/sienklogic/plan-build-run/add-phase"><img src="https://agentmods.dev/badge/commands/sienklogic/plan-build-run/add-phase.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.00009 | $0.00397 |
| Opus 5 | $0.00005 | $0.00198 |
| Sonnet 5 | $0.00002 | $0.00079 |
| Haiku 4.5 | $0.00001 | $0.00040 |
Grade A, and why
add-phase 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.
What it actually says
Handles:
- Phase number calculation (next sequential integer)
- Directory creation with slug generation
- Roadmap structure updates
- STATE.md roadmap evolution tracking
@.planning/ROADMAP.md @.planning/STATE.md
Extract phase description from $ARGUMENTS. If empty, ask user for a description.
2. Validate State
pbr-tools roadmap analyze
Check that ROADMAP.md exists and has at least one milestone.
3. Calculate Next Phase Number
Read ROADMAP.md, find the highest integer phase number in the current milestone, add 1.
4. Generate Slug
SLUG=$(pbr-tools generate-slug "$ARGUMENTS")
5. Create Phase Directory and Update Roadmap
pbr-tools roadmap append-phase --goal "$ARGUMENTS"
Create .planning/phases/{NN}-{slug}/ directory.
6. Update State
pbr-tools state record-activity "Added phase {NN}: {description}"
7. Commit
git add .planning/ROADMAP.md .planning/STATE.md .planning/phases/
git commit -m "docs: add phase {NN} — {slug}"
8. Report
Display: "Phase {NN}: {description} added to roadmap."
Suggest: /pbr:discuss-phase {NN} or /pbr:plan-phase {NN} as next steps.
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 · 76 lines · 9 tokens per session scan A 9ee6ea572803
add-phase is a command published in the GitHub repository SienkLogic/plan-build-run (17 stars, last pushed 5mo ago), licensed MIT. It adds 9 tokens to every session and 397 once invoked, about $0.0000 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
mesa-tecnica
Mesa técnica de expertos senior de desarrollo para decisiones de implementación, stack y código.
planning
Planning semanal de equipo con revisión de RFCs, priorización, asignación por responsable/pareja/squad y seguimiento.
poc
Modo Prueba de Concepto para validar viabilidad técnica antes de comprometer implementación completa.
tech-debt
Detectar y cuantificar deuda técnica con clasificación. Usa cuando el usuario dice "deuda técnica", "technical debt", "code smells", "refactorizar", "tech debt", "code rot", "spaghetti code", "duplicación", "complejidad ciclomática", "mantenibilidad". Incluye clasificación especial para AI slop. Genera reporte con…
auditar-seguridad
Auditoría de seguridad estática del código (OWASP Top 10, SecDevOps).
auto
Modo autónomo que ejecuta el pipeline SDD completo sin intervención humana. Usa cuando el usuario dice "auto", "autónomo", "autonomous", "run automatically", "ejecutar solo", "auto mode", "hands-off", "unattended", "modo piloto automático". Spawna agentes frescos por tarea para evitar context rot.