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 cblecker/claude-plugins --skill finalize-plangit clone --depth 1 https://github.com/cblecker/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/cblecker/claude-plugins/finalize-plan)<a href="https://agentmods.dev/skills/cblecker/claude-plugins/finalize-plan"><img src="https://agentmods.dev/badge/skills/cblecker/claude-plugins/finalize-plan/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/cblecker/claude-plugins/finalize-plan"><img src="https://agentmods.dev/badge/skills/cblecker/claude-plugins/finalize-plan.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.00057 | $0.00336 |
| Opus 5.5 | $0.00023 | $0.00134 |
| Sonnet 5.5 | $0.00011 | $0.00067 |
| Haiku 4.5 | $0.00006 | $0.00034 |
Grade A, and why
finalize-plan 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
Pre-flight: confirm plan mode
Check your system context for a "Plan mode is active" reminder. If you are not in plan mode, tell the user and stop — this skill only applies during planning.
Review the plan
Read the plan file (path is in the plan-mode system reminder).
Scan the conversation for details that a fresh context with only the plan file would need to faithfully execute the work. Focus on:
- Decisions — choices the user made between alternatives
- User corrections — anything the user said "no, do it this way" about
- Specific names — files, functions, types, CLI flags, tools, or MCP resources the user referenced or you agreed to use
- Commands — exact build/test/run commands the user specified
- Constraints — ordering, compatibility, "don't touch X", style preferences
Skip anything a competent agent can rediscover from the repository itself (line numbers, import paths, boilerplate structure, surrounding code context).
Report
If the plan already covers everything: say so in one sentence.
Otherwise list what's missing — brief bullets, each naming the gap and suggesting what to add. Then offer to update the plan file with the missing details.
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 Changed · +1 lines · +17 tokens per session 9b0c9434016f
- 1mo ago First seen · 39 lines · 40 tokens per session scan A 381ec65e1939
finalize-plan is a skill published in the GitHub repository cblecker/claude-plugins (5 stars, last pushed 17d ago), licensed Apache-2.0. It adds 57 tokens to every session and 336 once invoked, about $0.0002 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…