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 dyor/skills --skill create-planning-skillgit clone --depth 1 https://github.com/dyor/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/dyor/skills/create-planning-skill)<a href="https://agentmods.dev/skills/dyor/skills/create-planning-skill"><img src="https://agentmods.dev/badge/skills/dyor/skills/create-planning-skill/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/dyor/skills/create-planning-skill"><img src="https://agentmods.dev/badge/skills/dyor/skills/create-planning-skill.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.00083 | $0.02006 |
| Opus 5.5 | $0.00033 | $0.00802 |
| Sonnet 5.5 | $0.00017 | $0.00401 |
| Haiku 4.5 | $0.00008 | $0.00201 |
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 5d 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 — 99 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 blueprint 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.
Core Architectural Rule: Keep Active Plans Outside of .skills/
The .skills/ directory (and the upstream dyor/skills repo) is strictly for reusable, upstream-synced skill templates and scripts so skills can be periodically refreshed via import-skill or skills-repo-sync without clobbering project work.
- Blueprint definitions live in the skills repository under
planning-skills/<planning-skill-name>/(or when imported into a consumer project, under.skills/imported-skills/planning-skills/<planning-skill-name>/). - Project-specific materialized plans (the tailored guide, validation plan, progress report, and local hints generated when running a planning skill in an app repo) MUST NEVER be written inside
.skills/. Instead, they are materialized into a configurable project directory outside of.skills/— defaulting to<plan_dir>=plans/<planning-skill-name>/(or another directory chosen by the developer, such asSPECS/plans/<planning-skill-name>/).
Execution Protocol
Step 1: Solicit Planning Skill Name & Authoring Location
- Ask the developer for a new planning skill name in kebab-case (e.g.,
feature-auth,database-migration). - Determine where the blueprint collection itself is being authored:
- If authoring inside the
dyor/skillsrepository, create it atplanning-skills/<planning-skill-name>/. - If scaffolding locally inside an app repo, ask where to place the blueprint definition (defaulting to
planning-skills/<planning-skill-name>/or.skills/planning-skills/<planning-skill-name>/only if explicitly authoring a skill).
- If authoring inside the
Step 2: Scaffold Blueprint Directories
Once the developer provides <planning-skill-name>, create the following directory structure inside the blueprint root (planning-skills/<planning-skill-name>/):
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.
- 5d ago Changed · +15 lines · +30 tokens per session 062dec728423
- 2mo ago First seen · 84 lines · 53 tokens per session scan A 4351a4484047
create-planning-skill is a skill published in the GitHub repository dyor/skills (5 stars, last pushed today), licensed MIT. It adds 83 tokens to every session and 2,006 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-31.
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.