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 Vershub/ai-skills --skill plan-megit clone --depth 1 https://github.com/Vershub/ai-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/vershub/ai-skills/plan-me)<a href="https://agentmods.dev/skills/vershub/ai-skills/plan-me"><img src="https://agentmods.dev/badge/skills/vershub/ai-skills/plan-me/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/vershub/ai-skills/plan-me"><img src="https://agentmods.dev/badge/skills/vershub/ai-skills/plan-me.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.00074 | $0.02616 |
| Opus 5 | $0.00037 | $0.01308 |
| Sonnet 5 | $0.00015 | $0.00523 |
| Haiku 4.5 | $0.00007 | $0.00262 |
Grade A, and why
plan-me 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 8d 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 — 307 lines — stays where its author put it; the contents beside it link to each section on GitHub.
plan-me
Produces a comprehensive, multi-file implementation plan for a feature after conducting a detailed requirements interview with the user.
When to trigger
ONLY trigger on the literal command /plan-me (case-insensitive), optionally followed by a feature name:
/plan-me✅/plan-me user-authentication✅/Plan-Me checkout-flow✅
Do NOT trigger on natural-language planning requests like "help me plan X", "make a plan for Y", "I need a plan", etc. The user chose an explicit command precisely to avoid accidental activation.
If the command appears mid-conversation in any other context (e.g. the user is quoting it, asking what it does), do not start the workflow — just answer the question.
Workflow overview
- Get the feature name (from the command or by asking)
- Determine output location (JetBrains vs other)
- Conduct the interview (one question at a time, ~12 topics)
- Propose phase breakdown and confirm with user
- Generate files (main
PLAN.md+ one file per phase) - Present the result
Follow each step in order. Do not skip the interview to save time — the quality of the plan depends entirely on the depth of information gathered.
Step 1: Get the feature name
If the user typed /plan-me <name>, use that name. Normalize it to kebab-case (e.g. User Authentication → user-authentication).
If they typed only /plan-me, ask:
What's the name of the feature you want to plan? (Short, descriptive — I'll use it for the folder name.)
Wait for the answer before proceeding.
Step 2: Determine output location
Check whether the project root contains a .idea/ directory:
ls -la .idea/ 2>/dev/null
- If
.idea/exists → output path is.idea/plans/<feature-name>/(This is a JetBrains IDE project. The.idea/folder is typically gitignored, so plans stay local. They'll be visible in the IDE's project tree.) - If
.idea/does not exist → output path isdocs/<feature-name>/
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.
- 8d ago First seen · 307 lines · 74 tokens per session scan A 2995a21dc3f8
plan-me is a skill published in the GitHub repository Vershub/ai-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 74 tokens to every session and 2,616 once invoked, about $0.0004 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-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…
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…