agentmods.dev

plan

plan is a skill for Claude Code from mp-web3/claude-starter-kit. It costs 55 tokens per session (824 once invoked), scanned A, original, MIT.

A structured process for exploring, planning, building, and checking changes to a project, skill, script, or other major feature.

In plain words
What is it for?
Use it when adding features, creating skills, building scripts, or making architectural changes that need research, approval, implementation, and verification.
Why use it?
It reduces the risk of starting implementation without understanding the existing project or agreeing on the design.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions CLAUDE.md; names the AskUserQuestion tool.

not rated 109repo 7mo ago A scan 55 tokens original MIT

Good fit Use it when adding features, creating skills, building scripts, or making architectural changes that need research, approval, implementation, and verification.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mp-web3/claude-starter-kit/plan-and-implement
View source ↗ mp-web3/claude-starter-kit
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 mp-web3/claude-starter-kit --skill plan-and-implement
Clone the repo
git clone --depth 1 https://github.com/mp-web3/claude-starter-kit

Made for: Claude Code.

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.

agentmods badge for plan

README.md
[![agentmods](https://agentmods.dev/badge/skills/mp-web3/claude-starter-kit/plan-and-implement/github.svg)](https://agentmods.dev/skills/mp-web3/claude-starter-kit/plan-and-implement)
Your own site
<a href="https://agentmods.dev/skills/mp-web3/claude-starter-kit/plan-and-implement"><img src="https://agentmods.dev/badge/skills/mp-web3/claude-starter-kit/plan-and-implement/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.

agentmods 80×15 button for plan

Your own site · 80×15
<a href="https://agentmods.dev/skills/mp-web3/claude-starter-kit/plan-and-implement"><img src="https://agentmods.dev/badge/skills/mp-web3/claude-starter-kit/plan-and-implement.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 824 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00055 $0.00824
Opus 5.5 $0.00022 $0.00330
Sonnet 5.5 $0.00011 $0.00165
Haiku 4.5 $0.00006 $0.00082

Measured 1mo ago against content hash 20eb91dc9844, 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-and-implement/SKILL.md · 108 lines

How it starts

The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Plan & Implement Workflow

First: Read LEARNINGS.md (in this skill's directory) before proceeding.

You are executing a structured 6-phase workflow for building or changing project features. Follow each phase in order. Do NOT skip phases or start implementing before approval.

The user's request: $ARGUMENTS

Phase 1: Explore

Understand the current project state before designing anything.

  1. Read CLAUDE.md for project conventions, key paths, and existing skills
  2. Look for a file map or project structure documentation
  3. Read any existing skills, scripts, or files that relate to what's being built
  4. Identify reusable patterns, utilities, or templates from existing code

Do NOT propose anything yet — just gather context.

Phase 1.5: Tool Discovery (autonomy-first)

Before designing a custom solution, search for existing tools that do the job.

  1. Search for MCP servers — WebSearch for "<service-name> MCP server" on GitHub/npm/PyPI
  2. Search for official SDKs — Check if the service has an official Python/Node SDK
  3. Check existing MCP servers — Read .mcp.json for already-connected servers
  4. Evaluate options: MCP server > official SDK > custom wrapper
  5. If an MCP server exists: configure it in .mcp.json instead of writing custom code
  6. If no MCP server: proceed with custom implementation but note it as a future improvement target

Phase 2: Design

Classify what's being built and design the implementation.

  1. Classify the change type: skill / script / database / config / structure / other
  2. List files to create (with paths) and files to modify
  3. Define dependencies between files (what must be created first)
  4. Detail the design based on type
  5. Ask clarifying questions via AskUserQuestion if requirements are ambiguous — do NOT guess

Phase 3: Approve

Present the plan and wait for explicit approval.

Format the plan as:

What

  • Files to create (path + one-line description each)
  • Files to modify (path + what changes)

Read the full file on GitHub · 108 lines

Files

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.

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.

  1. 1mo ago First seen · 108 lines · 55 tokens per session scan A 20eb91dc9844

Subscribe to this mod's changes

plan is a skill published in the GitHub repository mp-web3/claude-starter-kit (109 stars, last pushed 7mo ago), licensed MIT. It adds 55 tokens to every session and 824 once invoked, about $0.0002 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.

Building agentsPlanning
Related

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…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens