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 threadgit 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/thread)<a href="https://agentmods.dev/skills/sienklogic/plan-build-run/thread"><img src="https://agentmods.dev/badge/skills/sienklogic/plan-build-run/thread/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/thread"><img src="https://agentmods.dev/badge/skills/sienklogic/plan-build-run/thread.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.00020 | $0.00502 |
| Opus 5.5 | $0.00008 | $0.00201 |
| Sonnet 5.5 | $0.00004 | $0.00100 |
| Haiku 4.5 | $0.00002 | $0.00050 |
Grade A, and why
thread 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.
What it actually says
STOP — DO NOT READ THIS FILE. You are already reading it.
/pbr:thread — Persistent Context Threads
Lightweight cross-session knowledge stores for work spanning multiple sessions that doesn't belong to any specific phase. Lighter than /pbr:pause (no phase state), richer than /pbr:note (structured sections).
Step 0 — Banner
╔══════════════════════════════════════════════════════════════╗
║ PLAN-BUILD-RUN ► THREAD ║
╚══════════════════════════════════════════════════════════════╝
Subcommands
/pbr:thread <name> — Create thread
mkdir -p .planning/threads- Generate slug from name
- Write
.planning/threads/{slug}.md:
---
created: {ISO date}
updated: {ISO date}
status: active
---
# {Thread Name}
## Goal
{What this thread is tracking — ask user}
## Context
{Current state of the work — filled during creation}
## References
{Related files, phases, decisions — gathered from conversation}
## Next Steps
{What to do next — filled during creation}
- Display:
Thread created: {name}
/pbr:thread list — List threads
Scan .planning/threads/*.md, display name + status + last updated.
/pbr:thread resume <name> — Resume thread
- Find
.planning/threads/{slug}.md - Read and display Goal, Context, References, Next Steps
- Thread context is now in the conversation — work can continue
- Update the
updatedfield in frontmatter
/pbr:thread close <name> — Close thread
Update status to closed. Optionally promote to phase or backlog.
Anti-Patterns
- DO NOT use threads for phase-specific work — use pause/resume instead
- DO NOT create threads for one-off notes — use /pbr:note instead
- DO NOT auto-close threads — always ask user
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 · 74 lines · 20 tokens per session scan A 9dffc0b6bc30
thread is a skill published in the GitHub repository SienkLogic/plan-build-run (19 stars, last pushed 6mo ago), licensed MIT. It adds 20 tokens to every session and 502 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.
plan-pipeline
Orchestrates the complete planning pipeline: product direction (ceo-review) -> architecture (eng-review) -> implementation plan (start) -> validation (validate) -> execution (execute). Run stages individually or let the orchestrator coordinate the full flow.
routines-discover
Analyzes the current project to surface high-value Routines use cases across the three trigger types (schedule, API, GitHub events). Usage: /routines-discover.
notion-governance
Governance for the Clybor life-CRM Notion workspace from a build repo. Use whenever a request touches Notion — logging a decision, creating or closing a task, reading project or client state, filing a note or KB entry, or invoking any notion-search / notion-fetch / notion-create-pages / notion-update-page tool.…
build-evaluate
Verify a completed build against the PRD's anchor case and success criteria. Runs the acceptance test and anchor-case check (serial across drivers sharing a write root), fans out 2-3 read-only cold-read agents (fresh-eyes, anti-scope-creep, drift-vs-mirror). On FAIL, auto-invokes five-whys for root-cause. On PASS with…
meeting-workflow
Transform meeting transcripts (pasted text, .vtt/.srt/.txt uploads, or your meeting tool's export) into structured records — a summary note with decisions and open questions, plus tracked tasks for every action item. Use whenever the user pastes or uploads a meeting transcript, says "log this meeting", "process this…