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/reapply-patches)<a href="https://agentmods.dev/commands/sienklogic/plan-build-run/reapply-patches"><img src="https://agentmods.dev/badge/commands/sienklogic/plan-build-run/reapply-patches/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/sienklogic/plan-build-run/reapply-patches"><img src="https://agentmods.dev/badge/commands/sienklogic/plan-build-run/reapply-patches.svg" alt="Reviewed on agentmods" width="80" 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.00009 | $0.00302 |
| Opus 5 | $0.00005 | $0.00151 |
| Sonnet 5 | $0.00002 | $0.00060 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
reapply-patches 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
PATCHES_DIR="${HOME}/.claude/pbr-local-patches"
if [ ! -d "$PATCHES_DIR" ]; then
PATCHES_DIR="./.claude/pbr-local-patches"
fi
Read backup-meta.json from the patches directory.
If no patches found: "No local patches found. Nothing to reapply." Exit.
2. Show Patch Summary
List all backed-up files with status.
3. Merge Each File
For each file in backup-meta.json:
- Read backed-up version (user's modified copy)
- Read newly installed version (current file after update)
- Compare and merge:
- Identical: skip (modification incorporated upstream)
- Different: identify user modifications, apply to new version
- Conflict: show both versions, ask user which to keep
4. Report
Display merge results table with status per file.
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 · 48 lines · 9 tokens per session scan A f3a97615c336
reapply-patches 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 302 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-09-03.
Other commands, from other repositories
worktree
Create a git worktree for isolated feature/fix work.
changelog
View recent CHANGELOG entries.
webhook
Configurar triggers externos (GitHub, Slack, Linear, PagerDuty) para automatizar comandos Don Cheli. Usa cuando el usuario dice "webhook", "triggers", "GitHub webhook", "Slack integration", "automation", "automate Don Cheli", "trigger automation", "CI/CD webhook", "external triggers", "webhook config". Configura…
changelog-auto
Auto-generar entradas de CHANGELOG.md desde commits convencionales. Usa cuando el usuario dice "generar changelog", "update changelog", "changelog", "conventional commits", "auto changelog", "release notes", "generar release notes", "伽 changelog". Genera entradas desde conventional commits (feat, fix, docs, etc.) con…
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…
guardian
Revisión de código IA como pre-commit hook — Guardian Angel.