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 skills add SienkLogic/plan-build-run --skill helpgit 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/skills/sienklogic/plan-build-run/help)<a href="https://agentmods.dev/skills/sienklogic/plan-build-run/help"><img src="https://agentmods.dev/badge/skills/sienklogic/plan-build-run/help/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/skills/sienklogic/plan-build-run/help"><img src="https://agentmods.dev/badge/skills/sienklogic/plan-build-run/help.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.00014 | $0.01709 |
| Opus 5.5 | $0.00006 | $0.00684 |
| Sonnet 5.5 | $0.00003 | $0.00342 |
| Haiku 4.5 | $0.00001 | $0.00171 |
Grade A, and why
help 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
STOP — DO NOT READ THIS FILE. You are already reading it. This prompt was injected into your context by Claude Code's plugin system. Using the Read tool on this SKILL.md file wastes tokens. Begin executing Step 1 immediately.
Step 0 — Immediate Output
Before ANY tool calls, display this banner:
╔══════════════════════════════════════════════════════════════╗
║ PLAN-BUILD-RUN ► COMMAND REFERENCE ║
╚══════════════════════════════════════════════════════════════╝
Then proceed to Step 1.
/pbr:help — Plan-Build-Run Command Reference
Step 1 — Contextual Help (Single Command)
If $ARGUMENTS contains a command name (e.g., plan, build, review, config, quick), show detailed help for just that command:
- Run this command to get metadata for the requested skill:
pbr-tools skill-metadata $ARGUMENTS
-
Parse the JSON response.
-
If the response contains a
namefield (success): Display a formatted detail block:
| Field | Value |
|---|---|
| Command | /pbr:{name} |
| Description | {description} |
| Arguments | {argument_hint} (or "None" if empty) |
| Allowed Tools | {allowed_tools} joined with ", " |
-
If the response contains an
errorfield (not found): Tell the user the command was not found. List available commands from theavailablearray, formatted as/pbr:{name}. -
STOP after displaying single-skill help. Do not continue to Step 2.
Step 2 — Full Help (All Commands)
If no argument was provided, display the full command reference:
- Run this command to get all skills:
pbr-tools help
-
Parse the JSON response. The result has a
.skillsarray of objects withname,description, andargument_hintfields. -
Group the skills into these categories based on skill name:
- Core Workflow: begin, plan, build, review, test
- Planning & Discovery: explore, discuss, import, scan, list-phase-assumptions
- Execution: quick, continue, autonomous, do
- Verification & Debugging: debug, health, validate-phase, ui-review, ui-phase
- Session Management: status, pause, resume, undo, continue
- Project Management: milestone, todo, note, config, setup, release, ship
- Analysis & Utilities: audit, audit-fix, dashboard, intel, profile, profile-user, session-report, statusline
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.
- 1mo ago First seen · 159 lines · 14 tokens per session scan A 10aeb68e2765
help is a skill published in the GitHub repository SienkLogic/plan-build-run (19 stars, last pushed 6mo ago), licensed MIT. It adds 14 tokens to every session and 1,709 once invoked, about $0.0001 per session on Opus 5.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 skills, from other repositories
issue-triage
3-phase issue backlog management with audit, deep analysis, and validated triage actions. Use when triaging GitHub issues, sorting bug reports, cleaning up stale tickets, or detecting duplicate issues. Args: 'all' to analyze all, issue numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit only.
self-assessment
Interactive skill assessment with personalized learning path generation.
talk-stage5-script
Produces a complete 5-act pitch with speaker notes, a slide-by-slide specification, and a ready-to-paste Kimi prompt for AI slide generation. Requires validated angle and title from Stage 4. Use when you have a confirmed talk angle and need the full script, slide spec, and AI-generated presentation prompt.
talk-stage6-revision
Produces revision sheets with quick navigation by act, a master concept-to-URL table, Q&A cheat-sheet with 6-10 anticipated questions, glossary, and external resources list. Use when preparing for a talk with Q&A, creating shareable reference material for attendees, or building a safety-net glossary for live delivery.
talk-stage1-extract
Extracts and structures source material (articles, transcripts, notes) into a talk summary with narrative arc, themes, metrics, and gaps. Auto-detects REX vs Concept type. Use when starting a new talk from any source material or auditing existing material before committing to a talk.
talk-stage3-concepts
Builds a numbered, categorized concept catalogue from the talk summary and timeline, scoring each concept HIGH / MEDIUM / LOW for talk potential with optional repo enrichment. Use when you need a structured inventory of concepts before choosing a talk angle, or when assessing which ideas have the strongest…