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/fastnpx skills add SienkLogic/plan-build-run --skill fastgit 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/fast)<a href="https://agentmods.dev/skills/sienklogic/plan-build-run/fast"><img src="https://agentmods.dev/badge/skills/sienklogic/plan-build-run/fast.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.00024 | $0.00696 |
| Opus 5 | $0.00012 | $0.00348 |
| Sonnet 5 | $0.00005 | $0.00139 |
| Haiku 4.5 | $0.00002 | $0.00070 |
Grade A, and why
fast 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 — 95 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.
/pbr:fast — Inline Trivial Task Execution
Execute a trivial task directly in the current context. No subagents, no PLAN.md, no research. For tasks like: fix a typo, update a config value, add a missing import, rename a variable, add a .gitignore entry, bump a version.
Use /pbr:quick for anything needing multi-step planning, research, or verification.
Step 0 — Banner
╔══════════════════════════════════════════════════════════════╗
║ PLAN-BUILD-RUN ► FAST ║
╚══════════════════════════════════════════════════════════════╝
Step 1 — Parse Task
If $ARGUMENTS is empty, ask: "What's the quick fix? (one sentence)"
Store as the task description.
Step 2 — Scope Check
A task is trivial if it needs:
- 3 or fewer file edits
- No new dependencies or architecture changes
- No research needed
If the task seems non-trivial, say:
This looks like it needs planning. Use /pbr:quick instead:
/pbr:quick "{task description}"
And stop.
Step 3 — Execute Inline
Do the work directly:
- Read the relevant file(s)
- Make the change(s) using Edit or Write
- Verify the change works (run existing tests if applicable)
No PLAN.md. No Task() spawn. Just do it.
Step 4 — Commit
Stage specific files (NEVER git add .) and commit:
git add {specific files}
git commit -m "{type}(fast): {concise description}"
Use conventional commit types: fix, feat, docs, chore, refactor as appropriate.
Step 5 — Log to Quick Tasks
If .planning/quick/ exists, create a minimal tracking entry:
- Find next NNN: scan
.planning/quick/for highest existing number + 1 - Create
.planning/quick/{NNN}-fast-{slug}/PLAN.mdwith a one-line plan - Create
.planning/quick/{NNN}-fast-{slug}/SUMMARY.mdwith the commit hash and description
This ensures fast tasks appear in state tracking alongside quick tasks.
Step 6 — Report
╔══════════════════════════════════════════════════════════════╗
║ FAST ✓ ║
╚══════════════════════════════════════════════════════════════╝
{commit hash} — {commit message}
Files: {changed files}
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 · 95 lines · 24 tokens per session scan A 33573c31ad33
fast is a skill published in the GitHub repository SienkLogic/plan-build-run (17 stars, last pushed 5mo ago), licensed MIT. It adds 24 tokens to every session and 696 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
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-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-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".
doncheli-tech-panel
Convene a senior engineering expert panel to evaluate technical decisions. Activate when user mentions "tech panel", "technical discussion", "expert opinion", "architecture decision", "which technology", "should we use".