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/lucasnad27/claude-plugins/create-plannpx skills add lucasnad27/claude-plugins --skill create-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/create-plan)<a href="https://agentmods.dev/skills/lucasnad27/claude-plugins/create-plan"><img src="https://agentmods.dev/badge/skills/lucasnad27/claude-plugins/create-plan.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.00015 | $0.02401 |
| Opus 5 | $0.00008 | $0.01201 |
| Sonnet 5 | $0.00003 | $0.00480 |
| Haiku 4.5 | $0.00002 | $0.00240 |
Grade A, and why
create-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 today.
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. **Prefer slices the agent can verify itself** — things with automated tests, curl-able endpoints, or observable output. Save manual checkpoints for things that genuinely need human eyes (UX feel, visual design, busine How it starts
The opening of the file, as written. The whole thing — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implementation Plan
You are tasked with creating detailed, vertical implementation plans from an approved design document. The design decisions are already made — your job is to translate them into actionable phases.
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" plan
Initial Response
When this command is invoked:
-
Check if parameters were provided:
- If a design doc path was provided as $ARGUMENTS, read it FULLY
- Also check for and read any referenced research docs or tickets
- Begin the planning process
-
If no parameters provided, respond with:
I'll help you create an implementation plan. Please provide: 1. The design document (from /design-doc) — required 2. Optionally, the research doc or ticket reference Tip: /create-plan .rpi/2026-01-05-auth-redesign-design.mdThen wait for the user's input.
Process
Step 1: Context Gathering
- Read the design document FULLY — this is your primary input
- Read any concrete reference artifact it links — an HTML mockup, a schema diff, example request/response payloads. These are the spec; prefer them over the prose describing them.
- Read any referenced research docs and tickets
- Spawn focused research agents if needed:
- Use codebase-locator to find specific files referenced in the design
- Use codebase-analyzer to understand implementation details needed for planning
- Only research what the design doc doesn't already cover
- Read all files identified by research agents
Step 2: Create Plan Outline
Present a high-level outline of vertical phases before writing the full plan:
Based on the design document, here's my proposed phasing:
Phase 1: [Name] — [What it accomplishes end-to-end]
Testing: [How this phase will be verified]
Phase 2: [Name] — [What it accomplishes end-to-end]
Testing: [How this phase will be verified]
Phase 3: [Name] — [What it accomplishes end-to-end]
Testing: [How this phase will be verified]
Does this phasing make sense? Should I adjust?
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.
- today Changed · +14 lines 4ea20ba1c2b6
- 5d ago First seen · 189 lines · 15 tokens per session scan A 47d14d4ff9a6
create-plan is a skill published in the GitHub repository lucasnad27/claude-plugins (3 stars, last pushed 5d ago), licensed MIT. It adds 15 tokens to every session and 2,401 once invoked, about $0.0001 per session on Opus 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…