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 vignesh2027/AI-AGENT-SKILLS --skill planning-and-task-breakdowngit clone --depth 1 https://github.com/vignesh2027/AI-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/skills/vignesh2027/ai-agent-skills/planning-and-task-breakdown)<a href="https://agentmods.dev/skills/vignesh2027/ai-agent-skills/planning-and-task-breakdown"><img src="https://agentmods.dev/badge/skills/vignesh2027/ai-agent-skills/planning-and-task-breakdown/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/vignesh2027/ai-agent-skills/planning-and-task-breakdown"><img src="https://agentmods.dev/badge/skills/vignesh2027/ai-agent-skills/planning-and-task-breakdown.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.00016 | $0.00675 |
| Opus 5.5 | $0.00006 | $0.00270 |
| Sonnet 5.5 | $0.00003 | $0.00135 |
| Haiku 4.5 | $0.00002 | $0.00068 |
Grade A, and why
planning-and-task-breakdown 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 2mo 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
Good task breakdown is the difference between a project that ships incrementally and one that delivers a big-bang surprise at the deadline. Tasks must be atomic (one logical unit), verifiable (you can prove it's done), and independent (completable without blocking on other tasks).
When to Use
- After writing a spec, before starting implementation
- When estimating a project
- When coordinating work across multiple engineers
- When a task has been "in progress" for more than 2 days
Process
Step 1: Identify vertical slices
A vertical slice delivers end-to-end value: from input to storage to output. Prefer slices over horizontal layers (don't plan "do all the models, then all the controllers, then all the views").
Step 2: Write tasks in the format: [Verb] [Object] [Constraint]
Good: "Add rate limiting to the /api/search endpoint (max 100 req/min per user)" Bad: "Rate limiting"
Step 3: Apply the two-day rule
No task should take more than 2 days. If it does, break it down further. If it genuinely can't be broken down, flag it as a risk.
Step 4: Define done for each task
Each task must have a clear, observable "done" state: test passes, endpoint returns 200, UI renders without error, migration runs cleanly.
Step 5: Identify dependencies
Draw or list which tasks must complete before others can start. Minimize dependencies — they are schedule risk.
Step 6: Identify the critical path
The longest chain of dependent tasks sets the minimum delivery time. Optimize this chain first.
Step 7: Add a buffer
Add 20% time to estimates for unknowns. If you've never done something before, add 50%.
Step 8: Sequence for early learning
Put the riskiest tasks first. You want to discover impossible requirements on day 2, not day 20.
Anti-Rationalizations
"These tasks are too small to track" If it's too small to track, it's too small to lose track of — which means it will be forgotten. Track it.
"I'll figure out the subtasks as I go" Figuring out subtasks during execution means context-switching between planning mode and execution mode. Do the planning upfront.
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.
- 2mo ago First seen · 73 lines · 16 tokens per session scan A 1ccd6cdb21d4
planning-and-task-breakdown is a skill published in the GitHub repository vignesh2027/AI-AGENT-SKILLS (2 stars, last pushed 2mo ago), licensed MIT. It adds 16 tokens to every session and 675 once invoked, about $0.0001 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.
planning-and-task-breakdown compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| planning-and-task-breakdownvignesh2027/AI-AGENT-SKILLS | Skill | 2 | 2mo ago | MIT | A | 16 | Claude Code, Codex |
| cw-gatesHmbown/Codewhale | Skill | 41k | 1mo ago | MIT | A | 48 | Claude Code, Codex |
| feishuHmbown/CodeWhale | Skill | 41k | 6d ago | MIT | A | 33 | Claude Code, Codex |
| eval-dataset-designbojieli/ai-agent-book | Skill | 57k | 1mo ago | Apache-2.0 | A | 138 | Claude Code, Codex |
| memory-systembojieli/ai-agent-book | Skill | 57k | 1mo ago | Apache-2.0 | A | 95 | Claude Code, Codex |
| release-helperSahir619/fable-method | Skill | 2.3k | 1mo ago | MIT | A | 43 | Claude Code |
| loongsuite-pilot-insightalibaba/loongsuite-pilot | Skill | 242 | yesterday | Apache-2.0 | A | 111 | Claude Code, Codex |