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/join-discord)<a href="https://agentmods.dev/commands/sienklogic/plan-build-run/join-discord"><img src="https://agentmods.dev/badge/commands/sienklogic/plan-build-run/join-discord.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.00006 | $0.00070 |
| Opus 5 | $0.00003 | $0.00035 |
| Sonnet 5 | $0.00001 | $0.00014 |
| Haiku 4.5 | $0.00001 | $0.00007 |
Grade A, and why
join-discord 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 7d 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
Join the PBR Discord
Connect with other Plan-Build-Run users, get help, share what you're building, and stay updated.
Invite link: https://discord.gg/5JJgD5svVS
Click the link or paste it into your browser to join.
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.
- 7d ago First seen · 12 lines · 6 tokens per session scan A 073ccac1cafe
join-discord is a command published in the GitHub repository SienkLogic/plan-build-run (17 stars, last pushed 5mo ago), licensed MIT. It adds 6 tokens to every session and 70 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
boldguy-linkedin-answer
Draft a LinkedIn comment on a post, referencing the guide's relevant section, in Flow style with AI markers removed.
worktree
Create a git worktree for isolated feature/fix work.
planning
Planning semanal de equipo con revisión de RFCs, priorización, asignación por responsable/pareja/squad y seguimiento.
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…
auditar-seguridad
Auditoría de seguridad estática del código (OWASP Top 10, SecDevOps).
crear-skill
Crear, probar y mejorar skills de forma iterativa. Usa cuando el usuario dice "crear skill", "crear habilidad", "build skill", "create a skill", "skill development", "desarrollar skill", "nueva habilidad". Usa el workflow: draft → test → review → improve → repeat con evaluación cuantitativa y qualitative review.