create-plan

create-plan is a skill for Claude Code, Codex from foryourhealth111-pixel/Vibe-Skills. It costs 23 tokens per session (608 once invoked), scanned A, a copy of create-plan, Apache-2.0.

A guide for turning a coding request into a short, ordered implementation plan. It reviews the project context and constraints without changing files.

In plain words
What is it for?
Use it when someone explicitly asks for a plan for a coding task, including discovery, proposed changes, tests, and rollout steps.
Why use it?
It gives developers actionable steps before implementation and highlights what is included or excluded. It asks follow-up questions only when planning would otherwise be irresponsible.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when someone explicitly asks for a plan for a coding task, including discovery, proposed changes, tests, and rollout steps.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/foryourhealth111-pixel/vibe-skills/create-plan
About the project

Vibe-Skills is a collection and routing system that helps AI agents discover, select, and coordinate specialized skills for completing tasks. It is intended for agents that need to organize workflows across many installed capabilities. The catalogue entries are skills and an agent belonging to this system.

foryourhealth111-pixel/Vibe-Skills · 3,235 stars · on GitHub

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 foryourhealth111-pixel/Vibe-Skills --skill create-plan
Clone the repo
git clone --depth 1 https://github.com/foryourhealth111-pixel/Vibe-Skills

Made for: Claude Code, Codex.

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 create-plan

README.md
[![agentmods](https://agentmods.dev/badge/skills/foryourhealth111-pixel/vibe-skills/create-plan/github.svg)](https://agentmods.dev/skills/foryourhealth111-pixel/vibe-skills/create-plan)
Your own site
<a href="https://agentmods.dev/skills/foryourhealth111-pixel/vibe-skills/create-plan"><img src="https://agentmods.dev/badge/skills/foryourhealth111-pixel/vibe-skills/create-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.

agentmods 80×15 button for create-plan

Your own site · 80×15
<a href="https://agentmods.dev/skills/foryourhealth111-pixel/vibe-skills/create-plan"><img src="https://agentmods.dev/badge/skills/foryourhealth111-pixel/vibe-skills/create-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 608 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 98% copy Near-identical to another mod 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.00023 $0.00608
Opus 5 $0.00012 $0.00304
Sonnet 5 $0.00005 $0.00122
Haiku 4.5 $0.00002 $0.00061

Measured 12d ago against content hash bcccc37b168b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

create-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 12d 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.

Origin

This is a copy

98% identical to create-plan — 9 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

bundled/skills/create-plan/SKILL.md · 75 lines

How it starts

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

Create Plan

Goal

Turn a user prompt into a single, actionable plan delivered in the final assistant message.

Minimal workflow

Throughout the entire workflow, operate in read-only mode. Do not write or update files.

  1. Scan context quickly

    • Read README.md and any obvious docs (docs/, CONTRIBUTING.md, ARCHITECTURE.md).
    • Skim relevant files (the ones most likely touched).
    • Identify constraints (language, frameworks, CI/test commands, deployment shape).
  2. Ask follow-ups only if blocking

    • Ask at most 1–2 questions.
    • Only ask if you cannot responsibly plan without the answer; prefer multiple-choice.
    • If unsure but not blocked, make a reasonable assumption and proceed.
  3. Create a plan using the template below

    • Start with 1 short paragraph describing the intent and approach.
    • Clearly call out what is in scope and what is not in scope in short.
    • Then provide a small checklist of action items (default 6–10 items).
      • Each checklist item should be a concrete action and, when helpful, mention files/commands.
      • Make items atomic and ordered: discovery → changes → tests → rollout.
      • Verb-first: "Add…", "Refactor…", "Verify…", "Ship…".
    • Include at least one item for tests/validation and one for edge cases/risk when applicable.
    • If there are unknowns, include a tiny Open questions section (max 3).
  4. Do not preface the plan with meta explanations; output only the plan as per template

Plan template (follow exactly)

# Plan

<1–3 sentences: what we're doing, why, and the high-level approach.>

## Scope
- In:
- Out:

## Action items
[ ] <Step 1>
[ ] <Step 2>
[ ] <Step 3>
[ ] <Step 4>
[ ] <Step 5>
[ ] <Step 6>

## Open questions
- <Question 1>
- <Question 2>
- <Question 3>

Checklist item guidance

Good checklist items:

  • Point to likely files/modules: src/..., app/..., services/...
  • Name concrete validation: "Run npm test", "Add unit tests for X"
  • Include safe rollout when relevant: feature flag, migration plan, rollback note

Read the full file on GitHub · 75 lines

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. 12d ago First seen · 75 lines · 23 tokens per session scan A bcccc37b168b

Subscribe to this mod's changes

create-plan is a skill published in the GitHub repository foryourhealth111-pixel/Vibe-Skills (3,235 stars, last pushed 11d ago), licensed Apache-2.0. It adds 23 tokens to every session and 608 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to create-plan, differing in 9 lines, and is treated as a copy.