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 selmakcby/claude-agents-skills --skill plangit clone --depth 1 https://github.com/selmakcby/claude-agents-skillsWrote 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/selmakcby/claude-agents-skills/plan)<a href="https://agentmods.dev/skills/selmakcby/claude-agents-skills/plan"><img src="https://agentmods.dev/badge/skills/selmakcby/claude-agents-skills/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/selmakcby/claude-agents-skills/plan"><img src="https://agentmods.dev/badge/skills/selmakcby/claude-agents-skills/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.00041 | $0.00575 |
| Opus 5 | $0.00020 | $0.00287 |
| Sonnet 5 | $0.00008 | $0.00115 |
| Haiku 4.5 | $0.00004 | $0.00057 |
Grade A, and why
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 11d 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
Plan — Implementation Planning
When to trigger
- User requests new feature
- Refactor or architectural change on the table
- Before any non-trivial code change
- Keywords: "implement", "add", "build", "refactor", "design"
Principles
- Plan before code. Always.
- Files, not concepts. Name specific paths.
- Risks upfront. Surface them before they bite.
- Phases over marathons. Break big features into phases.
Process
- Clarify the goal. Ask questions only if truly blocked.
- Read relevant context. Existing code, similar features, project CLAUDE.md.
- Map dependencies. What does this touch? What order matters?
- Draft steps. Each step = action + file + acceptance criteria.
- Surface risks. What could go wrong? Mitigations?
- Estimate scope. S / M / L.
- Return the plan. Don't write code. Hand off to builder.
Output format
## Goal
<one sentence, outcome-focused>
## Why
<motivation — user need, business driver, compliance, tech debt>
## Steps
1. <action> — `<exact/file/path.ext>` — <how we know it's done>
2. <action> — `<file>` — <criteria>
3. ...
## Risks
- <risk> → <mitigation>
- <risk> → <mitigation>
## Dependencies
- <service/feature/decision this touches>
## Out of scope
- <explicitly not covered here>
## Scope
**S** (under a day) | **M** (1-3 days) | **L** (week+)
Rules
- Never write code. Your job is the map, not the journey.
- If a step is "figure it out", it's not a step — decompose further.
- If it's over 10 steps, probably needs phasing. Split it.
- Flag architectural conflicts with existing patterns explicitly.
- Acceptance criteria must be testable, not vague ("feels right" ≠ criteria).
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.
- 11d ago First seen · 73 lines · 41 tokens per session scan A 96f3eb7e6927
plan is a skill published in the GitHub repository selmakcby/claude-agents-skills (124 stars, last pushed 4mo ago), licensed MIT. It adds 41 tokens to every session and 575 once invoked, about $0.0002 per session on Opus 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-30.
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…
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
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…