A planning skill for software changes. It uses the actual source code to identify where a change belongs, what it affects, and which tests may be involved before coding begins.

Scoping features, refactors, and edits; tracing affected code; choosing insertion points; and ordering implementation and test steps.

It prevents plans based on guesses and helps reveal callers, dependencies, prior decisions, and possible breakage.

plan — Skill for Claude Code by TheWinci/mimirs

Install

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.

Any agent

npx skills add TheWinci/mimirs --skill plan

Clone the repo

git clone --depth 1 https://github.com/TheWinci/mimirs

Made for: Claude Code.

Or install mimirs, the plugin that ships this one along with the rest of its 11 skills, 3 hooks.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/thewinci/mimirs/plan/github.svg)](https://agentmods.dev/skills/thewinci/mimirs/plan)

Your own site

<a href="https://agentmods.dev/skills/thewinci/mimirs/plan"><img src="https://agentmods.dev/badge/skills/thewinci/mimirs/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/thewinci/mimirs/plan"><img src="https://agentmods.dev/badge/skills/thewinci/mimirs/plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 75 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 516 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00075	$0.00516
Opus 5.5	$0.00030	$0.00206
Sonnet 5.5	$0.00015	$0.00103
Haiku 4.5	$0.00007	$0.00052

Measured 1mo ago against content hash 19f335d0aa26, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

skills/plan/SKILL.md · 18 lines

What it actually says

Plan

Goal: a concrete, ordered plan grounded in real source — and the blast radius of each proposed change before writing it.

Understand the area — search "<feature/topic>" for the relevant files, then read_relevant "<behavior>" to read the actual functions/sections with line ranges. Don't plan against guessed code.
Where it lands — write_relevant "<what you're adding>" for the best insertion point (file + anchor) for new code; project_map(focus: <key file>) for how the target neighborhood connects.
Impact of the change — for each symbol you intend to modify: impact <symbol> (transitive callers as a pruned tree + the tests to run) so the plan accounts for every caller it ripples to. Widen with usages <symbol> (call sites) and dependents <file> (file-level importers). trace from=<a> to=<b> to confirm two symbols actually connect before relying on the path.
Prior decisions & caveats — search_checkpoints "<area>" and search_commits "<area>" so the plan doesn't undo a deliberate choice; get_annotations on the files you'll touch for known bugs, constraints, or "don't refactor until X".
Resolve open decisions — before drafting, surface the choices the source doesn't settle (approach, scope, naming, tradeoffs) and ask the user. Don't guess past a fork that changes the plan; one round of focused questions beats a plan built on a wrong assumption.
Draft the plan — ordered steps, each naming the file:line to edit, what changes, the callers it impacts (from step 3), and the tests to run. Call out risks and remaining open questions instead of hiding them.

Finish: present the plan for review before implementing — steps in order, impact per step, tests to run, prior decisions respected, each with a file:line citation. Let the user review before acting.

Changes

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 First seen · 18 lines · 75 tokens per session scan A 19f335d0aa26

Subscribe to this mod's changes

plan is a skill published in the GitHub repository TheWinci/mimirs (30 stars, last pushed 6d ago), licensed Apache-2.0. It adds 75 tokens to every session and 516 once invoked, about $0.0003 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-30.

Claude Code Planning ai-coding code-search llm-tools mcp mcp-server

research

Performs deep research on a topic via deepresearch. Simulates a multi-step research process and returns a comprehensive research result as a string.

study8677/repobrain · 32 tokens

memorix-sessions

Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether sessionstart is useful.

AVIDS2/memorix · 31 tokens

memorix-troubleshooting

Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.

AVIDS2/memorix · 36 tokens

azure-event-grid-webhooks

Receive and validate Azure Event Grid webhook deliveries. Use when setting up an Event Grid WebHook event handler, implementing the Microsoft.EventGrid.SubscriptionValidationEvent handshake (echo data.validationCode as validationResponse with HTTP 200), implementing the CloudEvents v1.0 HTTP OPTIONS abuse-protection…

hookdeck/webhook-skills · 148 tokens

formstack-webhooks

Receive and verify Formstack Forms webhooks (the "WebHook" submit action, aka "Send Data to an External URL"). Use when setting up a Formstack form submission webhook handler, debugging X-FS-Signature HMAC verification, handling application/x-www-form-urlencoded or JSON submission payloads, or working out which fields…

hookdeck/webhook-skills · 108 tokens

circleci-webhooks

Receive and verify CircleCI outbound webhooks. Use when setting up a CircleCI webhook handler, debugging circleci-signature verification, or handling the workflow-completed and job-completed events CircleCI sends when a workflow or job reaches a terminal state. CircleCI signs the raw body with HMAC-SHA256 and sends a…

hookdeck/webhook-skills · 150 tokens