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/scan)<a href="https://agentmods.dev/commands/sienklogic/plan-build-run/scan"><img src="https://agentmods.dev/badge/commands/sienklogic/plan-build-run/scan.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.00035 |
| Opus 5 | $0.00008 | $0.00017 |
| Sonnet 5 | $0.00003 | $0.00007 |
| Haiku 4.5 | $0.00002 | $0.00003 |
Grade A, and why
scan 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 4d 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:scan 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.
- 4d ago First seen · 6 lines · 16 tokens per session scan A e41bd1686ddf
scan 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 35 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-09-03.
Other commands, from other repositories
drift
Detectar divergencias entre specs Gherkin e implementación (spec drift). Usa cuando el usuario dice "spec drift", "drift detection", "spec vs código", "conformance check", "spec deviation", "código no matchea specs", "implementation diverged", "spec vs implementation", "verificar specs". Compara features implementadas…
time-travel
Debugger de razonamiento que muestra por qué el framework eligió cada modelo, skill y decisión. Usa cuando el usuario dice "time travel", "por qué eligió", "reasoning debug", "decision audit", "why this model", "razonamiento", "debug reasoning", "explain decision", "modelo elegido". Permite ajustar skills…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
detectar-ambiguedad
Detectar ambigüedades y contradicciones en specs de forma exhaustiva.
cerrar-sesion
Ritual de cierre de sesión con auditoría, calidad, aprendizajes y contexto para la próxima sesión.
diagnostico
Verificar la salud del setup de Don Cheli en el proyecto actual.