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/discussgit 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/discuss)<a href="https://agentmods.dev/commands/sienklogic/plan-build-run/discuss"><img src="https://agentmods.dev/badge/commands/sienklogic/plan-build-run/discuss.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.00016 | $0.00036 |
| Opus 5 | $0.00008 | $0.00018 |
| Sonnet 5 | $0.00003 | $0.00007 |
| Haiku 4.5 | $0.00002 | $0.00004 |
Grade A, and why
discuss 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
This command is provided by the pbr:discuss 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.
- 5d ago First seen · 6 lines · 16 tokens per session scan A 9032fe7ba091
discuss is a command published in the GitHub repository SienkLogic/plan-build-run (17 stars, last pushed 5mo ago), licensed MIT. It adds 16 tokens to every session and 36 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
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.
context-health
Dashboard de salud del contexto activo con predicción de degradación y recomendaciones de compactación. Usa cuando el usuario dice "context health", "salud del contexto", "degradation", "compactar contexto", "context overflow", "tokens", "session health", "compact", "contexto lleno". Monitorea degrdación del contexto…
data-policy
Documentar qué datos toca el framework, qué sale a APIs externas y generar política de privacidad. Usa cuando el usuario dice "data policy", "política de datos", "privacy policy", "datos sensibles", "GDPR", "data handling", "APIs externas", "external APIs", "qué datos se comparten". Mapea data flows y genera política…
especificar
Crear especificaciones Gherkin desde un requerimiento/requisito. Usa cuando el usuario dice "escribir specs", "especificar feature", "crear Gherkin", "escribir requerimientos", "write specs", "requirements to Gherkin", "escribir scenarios", "documentar feature en Gherkin". Genera DBML schema auto-máticamente para…
implementar
Ejecutar tareas TDD fase por fase dentro de Docker hasta que todos los tests pasen.