create-planning-skill

create-planning-skill is a skill for Claude Code, Codex from dyor/skills. It costs 53 tokens per session (1,458 once invoked), scanned A, original, MIT.

A scaffolding guide for creating a six-part planning skill inside a project's remote skills repository.

In plain words
What is it for?
Use it to create prompt, agent, guide, calculator, validation, and hints blueprints for a new planning skill named in kebab-case.
Why use it?
It provides the expected folders and instruction files needed to define a large, repeatable development effort.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions AGENTS.md.

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.

agentmods
npx agentmods add skills/dyor/skills/create-planning-skill
Any agent
npx skills add dyor/skills --skill create-planning-skill
Clone the repo
git clone --depth 1 https://github.com/dyor/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-planning-skill

README.md
[![agentmods](https://agentmods.dev/badge/skills/dyor/skills/create-planning-skill.svg)](https://agentmods.dev/skills/dyor/skills/create-planning-skill)
Your own site
<a href="https://agentmods.dev/skills/dyor/skills/create-planning-skill"><img src="https://agentmods.dev/badge/skills/dyor/skills/create-planning-skill.svg" alt="Measured on agentmods" height="20"></a>
Per session 53 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,458 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00053 $0.01458
Opus 5 $0.00026 $0.00729
Sonnet 5 $0.00011 $0.00292
Haiku 4.5 $0.00005 $0.00146

Measured 6d ago against content hash 4351a4484047, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

create-planning-skill 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 6d 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.

create-planning-skill/SKILL.md · 84 lines

How it starts

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

Skill: Create Planning Skill

Overview

A "Planning Skill" is a set of orchestrated skills that help a developer execute a massive chunk of work. This skill scaffolds the 6 essential blueprints required for a standard Planning Skill, mimicking the robust architecture of kmp-baseline.

Execution Protocol

Step 1: Solicit Planning Skill Name

Ask the developer for a new planning skill name. It must be formatted in kabab-case (e.g., feature-auth, database-migration).

Step 2: Scaffold Directories

Once the developer provides the name (referred to below as <planning-skill-name>), create the following directory structure inside .skills/planning-skills/<planning-skill-name>/:

  • <planning-skill-name>-prompt-blueprint/
  • <planning-skill-name>-agent-blueprint/
  • <planning-skill-name>-guide-blueprint/
  • <planning-skill-name>-calculator-blueprint/
  • <planning-skill-name>-validation-blueprint/
  • <planning-skill-name>-hints-blueprint/
  • <planning-skill-name>-hints-blueprint/examples/

Step 3: Scaffold Blueprint SKILL.md Files

Create a SKILL.md file inside each of the 6 directories you just created. Ensure that every scaffolded blueprint SKILL.md file begins with the following warning banner directly below the YAML front-matter:

[!WARNING] This is an immutable blueprint template that is used to build the active plans. Do not execute or edit this file directly while writing code for this codebase - only for building the active plans. For active execution, use .skills/planning-skills/

Use the following specifications to generate their content dynamically:

1. <planning-skill-name>-prompt-blueprint

Purpose: The entry point skill that tells the agent how to localize the blueprints into the developer's local .skills/planning-skills/<planning-skill-name>-local/ directory. Content Requirements:

  • Write a prompt instructing the agent to sequentially read the sibling blueprints using relative paths (e.g., ../<planning-skill-name>-guide-blueprint/SKILL.md) and generate their local, codebase-specific -local equivalents inside a completely new directory called .skills/planning-skills/<planning-skill-name>-local/ (e.g., .skills/planning-skills/<planning-skill-name>-local/<planning-skill-name>-guide-local/SKILL.md).
  • It must instruct the agent to prompt the host developer for specific variables needed to populate the local guides/hints (similar to soliciting the "App Name" and "Target Audience" in kmp-baseline).

Read the full file on GitHub · 84 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. 6d ago First seen · 84 lines · 53 tokens per session scan A 4351a4484047

Subscribe to this mod's changes

create-planning-skill is a skill published in the GitHub repository dyor/skills (5 stars, last pushed 3mo ago), licensed MIT. It adds 53 tokens to every session and 1,458 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

systematic-debugging

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

obra/superpowers · 21 tokens

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

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