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 skills/sienklogic/plan-build-run/donpx skills add SienkLogic/plan-build-run --skill dogit 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/do)<a href="https://agentmods.dev/skills/sienklogic/plan-build-run/do"><img src="https://agentmods.dev/badge/skills/sienklogic/plan-build-run/do.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.00014 | $0.01833 |
| Opus 5 | $0.00007 | $0.00916 |
| Sonnet 5 | $0.00003 | $0.00367 |
| Haiku 4.5 | $0.00001 | $0.00183 |
Grade A, and why
do 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 2d 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 — 166 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 ~3,000 tokens. Begin executing Step 1 immediately.
/pbr:do -- Freeform Task Router
You are running the do skill. Your job is to analyze freeform text from the user and route it to the most appropriate PBR skill. You are a dispatcher, not an executor -- you never do the work yourself.
Step 0 -- Immediate Output
Before ANY tool calls, display this banner:
╔══════════════════════════════════════════════════════════════╗
║ PLAN-BUILD-RUN ► DO ║
╚══════════════════════════════════════════════════════════════╝
Then proceed to Step 1.
Step 1 -- Validate Input
If $ARGUMENTS is empty, ask the user what they want to do via AskUserQuestion:
What would you like to do? Describe the task, bug, or idea and I'll route it to the right skill.
Step 2 -- Analyze and Route
Step 2a -- Gather Context
- Read
.planning/STATE.mdto getcurrent_phase,status,phase_slug. - Check if
.planning/ROADMAP.mdexists (sethasRoadmap). - Build context object:
{ activePhase: phase_slug, hasRoadmap: boolean }.
Step 2b -- Check Config
- Read
.planning/config.jsonif it exists. - Check
features.natural_language_routing(default:trueif absent). - Check
features.adaptive_ceremony(default:trueif absent). - Check
ceremony_level(default:"auto"if absent).
Step 2c -- Intent Classification
When NL routing is enabled (features.natural_language_routing is true or absent):
Score $ARGUMENTS against these route keyword groups:
| Route | Keywords | Weight |
|---|---|---|
| debug | bug, error, crash, fix, broken, failing, exception, stacktrace, debug | 1.0 |
| explore | explore, research, investigate, how does, how do, understand, analyze, compare | 1.0 |
| plan-phase | plan, architect, design, migrate, refactor across, redesign, system, new | 0.9 |
| quick | add, create, update, change, rename, remove, write test, implement, feature, refactor | 0.85 |
| note | remember, note, todo, idea, later, don't forget, remind | 1.0 |
| validate-phase | validate, coverage gaps, test gaps, missing tests, untested, requirement coverage | 1.0 |
| verify-work | review, check, verify, quality, looks right | 0.9 |
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.
- 2d ago First seen · 166 lines · 14 tokens per session scan A 3f3655e73992
do is a skill published in the GitHub repository SienkLogic/plan-build-run (17 stars, last pushed 5mo ago), licensed MIT. It adds 14 tokens to every session and 1,833 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 skills, from other repositories
tdd-rust
TDD workflow for RTK filter development. Red-Green-Refactor with Rust idioms. Real fixtures, token savings assertions, snapshot tests with insta. Auto-triggers on new filter implementation.
handoff-create
Generate a structured handoff document from the current session. Captures scope, relevant files with line numbers, key discoveries, work completed, current status, next steps, and code snippets. Use before ending a session or handing work to another agent.
handoff-update
Update an existing handoff document with current session progress. Applies section-specific merge rules: append-only for Work Done (never deletes history), replace for Status and Next Steps, merge for Files and Discoveries. Falls back to creating a new handoff if no source file is found.
handoff-resume
Load a handoff document and resume work from where a previous session left off. Parses scope, file references, completed work, and next steps, then confirms understanding before proceeding.
mission-slice-sop
Use when starting, building, handing off, restoring, or closing a mission or slice under the default lightweight SDLC.
doncheli-api-contract
Design complete API contracts covering endpoints, auth, rate limiting, error handling, retries, circuit breaker and idempotency. Activate when user mentions "api contract", "api design", "endpoint", "webhook", "REST", "GraphQL", "OpenAPI", "design the API".