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 shawnclybor/clybor-claude-tooling --skill task-plangit clone --depth 1 https://github.com/shawnclybor/clybor-claude-toolingWrote 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/shawnclybor/clybor-claude-tooling/task-plan)<a href="https://agentmods.dev/skills/shawnclybor/clybor-claude-tooling/task-plan"><img src="https://agentmods.dev/badge/skills/shawnclybor/clybor-claude-tooling/task-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.
<a href="https://agentmods.dev/skills/shawnclybor/clybor-claude-tooling/task-plan"><img src="https://agentmods.dev/badge/skills/shawnclybor/clybor-claude-tooling/task-plan.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.00086 | $0.01088 |
| Opus 5.5 | $0.00034 | $0.00435 |
| Sonnet 5.5 | $0.00017 | $0.00218 |
| Haiku 4.5 | $0.00009 | $0.00109 |
Grade A, and why
task-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 4d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Plan
Turn an accepted PRD into a flat, sequenced task list with checkboxes. The plan is the contract between the PRD and the implementation. Tasks too big = invisible progress; tasks too small = ceremonial overhead. Aim for one-focused-pass per task.
When to use
- Right after a PRD is written and accepted
- When picking up an existing PRD that lacks a plan
- When re-planning after a Stage 6 evaluation surfaces structural issues
Input
prd_path— path to the PRD (e.g.,docs/PRDs/oauth-token-refresh.md)
Output
docs/PRDs/<feature_slug>-plan.md, copied from templates/plan-template.md and filled in. Sections:
- Tasks — checkbox list with
Touches,Verifies,Check,Notesper task - Parallelizable groups — which tasks can run concurrently
- Risks per task
Sizing rules
Each task should pass these checks:
- One-pass completable — ≤ 2 hours of focused work
- Single responsibility — advances one concern; does not bundle unrelated changes
- Independent where possible — runs in parallel with siblings when safe
- Tied to a criterion — advances at least one PRD success criterion
- Testable in isolation — there is a check (unit test, integration test, smoke) that confirms this task alone is done
If a task fails any of these, split it.
Parallelizable-group analysis
After the flat task list is drafted, invoke task-distributor to produce the parallelizable-group section. It applies the safety rules:
- No shared write target between parallel tasks
- No read-after-write dependencies between parallel tasks
- No contended shared resources (DB row, rate limit, file lock)
Take the task-distributor output verbatim into the plan's "Parallelizable groups" section. The ralph-implement skill at Stage 4 reads this section to spawn parallel work.
Common decomposition patterns
| PRD shape | Plan shape |
|---|---|
| New feature | Schema → API → client → tests → docs |
| Refactor | Add new path → migrate callers in batches → remove old path |
| Integration | Contract / types → happy path → error paths → retries → observability |
| Bug fix | Reproduce → narrow → fix → regression test |
| Migration | Backup → write new state alongside old → verify equivalence → switch reads → drop old |
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.
- 4d ago Changed e4b1526345fe
- 1mo ago First seen · 89 lines · 86 tokens per session scan A e8f870ac028d
task-plan is a skill published in the GitHub repository shawnclybor/clybor-claude-tooling (6 stars, last pushed 5d ago), licensed MIT. It adds 86 tokens to every session and 1,088 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
autonomous
Run multiple phases hands-free. Chains discuss, plan, build, and verify automatically.
quick
Execute an ad-hoc task with atomic commits. Skips full plan/review.
audit
Review past Claude Code sessions for PBR workflow compliance and UX quality.
resume
Pick up where you left off. Restores context and suggests next action.
status
Show current project status and suggest what to do next.
config
Configure settings: depth, model profiles, features, git, and gates.