addyosmani/agent-skills is a collection of reusable workflows, quality checks, commands, and other instructions that guide AI coding agents through software development. It is for developers who want agents to follow consistent engineering practices, and the catalogue entries are its packaged skills, commands, agents, plugins, instructions, and hooks.
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 agentmods add commands/addyosmani/agent-skills/planninggit clone --depth 1 https://github.com/addyosmani/agent-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/commands/addyosmani/agent-skills/planning)<a href="https://agentmods.dev/commands/addyosmani/agent-skills/planning"><img src="https://agentmods.dev/badge/commands/addyosmani/agent-skills/planning.svg" alt="Measured on agentmods" 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.00000 | $0.00131 |
| Opus 5 | $0.00000 | $0.00066 |
| Sonnet 5 | $0.00000 | $0.00026 |
| Haiku 4.5 | $0.00000 | $0.00013 |
Grade A, and why
planning 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 2d 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.
This is a copy
86% identical to plan — 11 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.
What it actually says
description = "Break work into small verifiable tasks with acceptance criteria and dependency ordering"
prompt = """ Invoke the planning-and-task-breakdown skill.
Read the existing spec (SPEC.md or equivalent) and the relevant codebase sections. Then:
- Enter plan mode — read only, no code changes
- Identify the dependency graph between components
- Slice work vertically (one complete path per task, not horizontal layers)
- Write tasks with acceptance criteria and verification steps
- Add checkpoints between phases
- Present the plan for human review
Save the plan to tasks/plan.md and task list to tasks/todo.md. """
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.
- 2d ago First seen · 16 lines · 0 tokens per session scan A 0be6342ddff3
planning is a command published in the GitHub repository addyosmani/agent-skills (92,284 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 131 tokens. A static security scan graded it A with 0 findings. It is 86% identical to plan, differing in 11 lines, and is treated as a copy.
Other commands, from other repositories
ship
通过并行 fan-out 到 specialist personas 运行发布前 checklist，然后综合 go/no-go decision.
code-simplify
简化代码以提升清晰度和可维护性 — 在不改变行为的前提下降低复杂度.
review
执行五轴 code review — correctness、readability、architecture、security、performance.
build
增量实现下一个任务 — build、test、verify、commit.
plan
将工作拆解为带 acceptance criteria 和 dependency ordering 的小型可验证 tasks.
spec
启动 spec-driven development — 写代码前先编写结构化 specification.