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 franzos/claude-plugins --skill plan-rungit clone --depth 1 https://github.com/franzos/claude-pluginsWrote 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/franzos/claude-plugins/plan-run)<a href="https://agentmods.dev/skills/franzos/claude-plugins/plan-run"><img src="https://agentmods.dev/badge/skills/franzos/claude-plugins/plan-run/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/franzos/claude-plugins/plan-run"><img src="https://agentmods.dev/badge/skills/franzos/claude-plugins/plan-run.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.00070 | $0.01641 |
| Opus 5.5 | $0.00028 | $0.00656 |
| Sonnet 5.5 | $0.00014 | $0.00328 |
| Haiku 4.5 | $0.00007 | $0.00164 |
Grade A, and why
plan:run 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Executing a plan
$KBis your knowledge-base root: a directory outside the working repo holding<project>/specs/,<project>/plans/and<project>/checkpoints/. Point at it from your CLAUDE.md. Keeping these out of the repo keeps process artifacts from leaking into it, and the knowledge survives clones, branches and machines.
Run this in a fresh session. Execution in the same session that wrote the plan starts at 100k+ of context and pays that on every turn for the rest of the run.
Run it autonomously
Work the whole plan through without checking in. The user already signed the plan off. Do not ask permission to start a task, to move to the next one, or to act on the commit answer they give you in section 1.
Report at milestones, not per task - a short line when a group of related tasks lands, not a narration of each one.
There are exactly four reasons to stop and ask:
- The two run questions at the start (section 1), asked together, once.
- A task contradicts the spec, or doing it would change scope (section 3).
- Something is genuinely ambiguous and both readings lead to materially different work.
- The context thresholds below.
Anything else - a task that needs a small mechanical deviation, a pre-existing failure, a judgment call with an obvious default - decide it, note it, keep going.
1. Load
Find the plan under $KB/<project>/plans/. If several match, take the newest by date and say which one you took.
Check $KB/<project>/checkpoints/ first. If a checkpoint exists for this slug, this is a resume, not a fresh run - use /plan:resume instead.
Read, in this order: the spec, the plan, then the project's CLAUDE.md (repo root first, then $KB/<project>/CLAUDE.md). Read the files the plan names as you reach the tasks that touch them, not up front.
Record the starting state before touching anything: current branch, whether the tree is clean, and the current pass/fail count. This is the baseline you will compare against at the end.
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 · 119 lines · 70 tokens per session scan A f139025258a0
plan:run is a skill published in the GitHub repository franzos/claude-plugins (1 stars, last pushed 13d ago), licensed MIT. It adds 70 tokens to every session and 1,641 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
sxo
Search Experience Optimization (SXO), the bridge between SEO and UX/CRO. Audits the journey from the SERP click to the on-page goal: click-through factors (title, meta, rich results), then post-click signals that keep users and drive conversions: above-the-fold relevance and intent match, page speed / Core Web Vitals…
meta-tags-optimizer
Optimize title tags, meta descriptions, Open Graph, and Twitter cards for maximum click-through rate. Generates multiple A/B test variations with character counting and SERP preview. Use when asked to "optimize title tag", "write meta description", "improve CTR", "Open Graph tags", "fix my meta tags", "social media…
critical-code-reviewer
Rigorously review code or pull requests for correctness, security, accessibility, maintainability, tests, and edge cases. Use when users request a critical code review, want a guided walkthrough of findings, need implementer-facing feedback, or want to prepare, create, or submit a GitHub pull request review.
shiny-bslib
Build modern Shiny dashboards and applications using bslib (Bootstrap 5). Use when creating new Shiny apps, modernizing legacy apps (fluidPage, fluidRow/column, tabsetPanel, wellPanel, shinythemes), or working with bslib page layouts, grid systems, cards, value boxes, navigation, sidebars, filling layouts, theming…
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.