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 skills/nickpolyder/np.copilot.config/task-breakdownnpx skills add NickPolyder/NP.CoPilot.Config --skill task-breakdowngit clone --depth 1 https://github.com/NickPolyder/NP.CoPilot.ConfigWhat 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 | $0.00032 | $0.00985 |
| Opus 5 | $0.00016 | $0.00492 |
| Sonnet 5 | $0.00006 | $0.00197 |
| Haiku 4.5 | $0.00003 | $0.00098 |
Grade A, and why
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 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.
How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Intent (anchor): Convert an approved feature design into an ordered, dependency-aware
tasks.mdthat implementation can execute safely. Always: read the design thoroughly; group work into phases; order by dependency; mark independent work as parallelizable; include paired test work. Never: implement code, silently redesign the feature, or skip dependencies.
Shared policy: Follow
instructions/coordination.instructions.mdfor precedence, invocation, delegation, and handoffs. Applyinstructions/workflow.instructions.mdfor proportional work and verification.
You are translating an approved design into executable work that can be implemented in dependency order.
Your goals are to:
- Break down the design — turn design sections into concrete implementation and test tasks.
- Sequence work safely — make dependencies explicit and order tasks within each phase.
- Expose parallelism — mark independent tasks so multiple agents can work safely when appropriate.
- Prepare implementation — produce
tasks.mdsuitable forimplementation-runner.
When to use this skill
Use this skill whenever:
- A feature design has been approved and needs implementation tasks.
- The user asks for a
tasks.md, task list, work breakdown, estimates, or dependency ordering. - Implementation should be planned before code changes begin.
- You need the third atomic step in the chain:
codebase-research→feature-design-doc→task-breakdown→implementation-runner.
Do not use this skill for:
- Codebase research — use
codebase-research. - Writing or revising the feature design — use
feature-design-doc. - Executing tasks or editing production code — use
implementation-runner. - End-to-end orchestration — recommend
prd-workflow.
Workflow
Break the design into implementable tasks.
-
Read the design document thoroughly.
-
Generate
docs/features/{feature-name}/tasks.mdwith:- Phases — group tasks into logical phases (e.g., backend, frontend, integration).
- Task format — each task has: ID, title, description, acceptance criteria, estimated complexity (S/M/L), dependencies.
- Ordering — tasks within a phase are ordered by dependency. Independent tasks are marked as parallelizable.
- Test tasks — every implementation task has a corresponding test task or tests are included in the task itself.
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 · 106 lines · 32 tokens per session scan A db49df8ae106
task-breakdown is a skill published in the GitHub repository NickPolyder/NP.CoPilot.Config (2 stars, last pushed 7d ago), licensed MIT. It adds 32 tokens to every session and 985 once invoked, about $0.0002 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.
Other skills, from other repositories
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.
dot-ai-prd-create
Create documentation-first PRDs that guide development through user-facing content.
agent-upkeep
Perform one small, scoped maintenance improvement to the Elements monorepo and open a single reviewable pull request. Use this skill for scheduled or unattended upkeep runs that improve unit test coverage for one file, fix one behavioral bug in one module, or move one off ESLint rule toward enforcement to reduce…
organize-project
Organise documents into folders and move them between folders and modules with MOVE. Use when a module has grown unstructured, when restructuring a project, or when a document is in the wrong place.
smithers-supervise
Watch for stale running runs and auto-resume them. Run smithers supervise --help for usage details.