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/siarhei-belavus/agent-public/development-task-plannernpx skills add siarhei-belavus/agent-public --skill development-task-plannergit clone --depth 1 https://github.com/siarhei-belavus/agent-publicWrote 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/siarhei-belavus/agent-public/development-task-planner)<a href="https://agentmods.dev/skills/siarhei-belavus/agent-public/development-task-planner"><img src="https://agentmods.dev/badge/skills/siarhei-belavus/agent-public/development-task-planner.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.00059 | $0.01805 |
| Opus 5 | $0.00030 | $0.00903 |
| Sonnet 5 | $0.00012 | $0.00361 |
| Haiku 4.5 | $0.00006 | $0.00180 |
Grade A, and why
development-task-planner 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Development Task Planner
Turn ambiguous engineering work into a concrete implementation plan that is safe to execute, easy to review, and easy to evolve. Optimize for low-risk sequencing, clear ownership, explicit validation, and low human cognitive load.
Assume the plan will be followed strictly during implementation unless a human explicitly amends it. Assume the implementation may be executed by a different agent in a fresh context window with no access to the prior conversation, so the plan must be self-sufficient.
Planning Workflow
-
Establish scope.
- Clarify the exact task, desired outcome, constraints, and what is out of scope.
- Identify whether the ask is feature work, refactor, migration, bug fix, infrastructure work, or architecture change.
- Prefer concrete deliverables over vague goals.
-
Identify the true change surface.
- Find the core modules, state transitions, APIs, persistence, and tests that the task will affect.
- Distinguish direct change points from incidental neighbors.
- If the task is stateful or lifecycle-heavy, treat restart, retry, cancellation, and recovery as first-class planning concerns.
-
Define success before steps.
- State the observable behavior that must be true when the task is done.
- Define validation early: tests, checks, smoke paths, or user-visible outcomes.
- Call out unknowns, assumptions, and risks before proposing execution order.
-
Slice the work into low-risk increments.
- Prefer increments that keep the system working after each step.
- Isolate schema/model changes from behavior changes when possible.
- Separate foundational refactors from product behavior unless combining them is clearly safer.
- Favor plans that are easy to review and revert.
-
Plan for amendment, not improvisation.
- Make it explicit that implementation must stop if the plan becomes unsafe, impossible, or contradicted by the real codebase.
- Require an amendment flow: surface the blocker, list options, give pros/cons, explain plan impact, and wait for a human decision.
- If a better but non-essential design appears during implementation, require a
REVIEW_NOTErather than silent deviation.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 First seen · 174 lines · 59 tokens per session scan A c3d9a557b0a4
development-task-planner is a skill published in the GitHub repository siarhei-belavus/agent-public (2 stars, last pushed 3mo ago), licensed MIT. It adds 59 tokens to every session and 1,805 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…