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 lucasnad27/claude-plugins --skill implement-plangit clone --depth 1 https://github.com/lucasnad27/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/lucasnad27/claude-plugins/implement-plan)<a href="https://agentmods.dev/skills/lucasnad27/claude-plugins/implement-plan"><img src="https://agentmods.dev/badge/skills/lucasnad27/claude-plugins/implement-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/lucasnad27/claude-plugins/implement-plan"><img src="https://agentmods.dev/badge/skills/lucasnad27/claude-plugins/implement-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.00013 | $0.02971 |
| Opus 5.5 | $0.00005 | $0.01188 |
| Sonnet 5.5 | $0.00003 | $0.00594 |
| Haiku 4.5 | $0.00001 | $0.00297 |
Grade A, and why
implement-plan scanned grade A with 1 finding 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 25d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
2. Exercise the work yourself — start a server, run curl commands, call the API How it starts
The opening of the file, as written. The whole thing — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement Plan
You are tasked with implementing an approved technical plan (.rpi/plan-*.md). These plans contain phases with specific changes and success criteria.
Mark the herdr phase
As your very first action, tag this agent's herdr tab so the session navigator shows the workflow phase (safe no-op outside herdr):
bash "$(git rev-parse --show-toplevel)/.claude/scripts/herdr-phase.sh" implement
Getting Started
When given a plan path:
- Read the plan completely and check for any existing checkmarks (- [x])
- Read the original ticket and all files mentioned in the plan
- Read any concrete reference artifact the design linked — an HTML mockup, schema diff, or example payloads. Build against the artifact, not against prose describing it.
- Think carefully and step-by-step about how the pieces fit together — the plan is the spec, but real code rarely matches the plan exactly
- Create a todo list to track your progress
- Start implementing if you understand what needs to be done
If no plan path provided, ask for one.
This skill is designed for long-running autonomous execution. The plan provides complete upfront context — phases, file paths, verification commands — so the implementing agent can work end-to-end without progressive guidance. Users running this skill should consider enabling auto mode (Shift+Tab) to cut cycle time on multi-phase implementations.
Implementation Philosophy
Plans are carefully designed, but reality can be messy. Your job is to:
- Follow the plan's intent while adapting to what you find
- Implement each phase fully before moving to the next
- Verify your work makes sense in the broader codebase context
- Update checkboxes in the plan as you complete sections
- Fix the root cause, not the symptom. A phase that names a bug names a symptom. Before editing, check every caller of the function you're about to touch — one guard in the shared function is both the smaller diff and the real fix, where a guard per call site leaves every caller nobody filed a ticket about still broken.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 25d ago Changed · +1 lines 3cad2fe806ab
- 1mo ago Changed 46dc967b62dd
- 1mo ago Changed 42c092b86134
- 1mo ago First seen · 237 lines · 13 tokens per session scan A 47dfe0a28e1b
implement-plan is a skill published in the GitHub repository lucasnad27/claude-plugins (3 stars, last pushed 22d ago), licensed MIT. It adds 13 tokens to every session and 2,971 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). 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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…