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/ahmadulhoq/agentskel/task-plannernpx skills add ahmadulhoq/agentskel --skill task-plannergit clone --depth 1 https://github.com/ahmadulhoq/agentskelWrote 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/ahmadulhoq/agentskel/task-planner)<a href="https://agentmods.dev/skills/ahmadulhoq/agentskel/task-planner"><img src="https://agentmods.dev/badge/skills/ahmadulhoq/agentskel/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 | $0.00030 | $0.00532 |
| Opus 5 | $0.00015 | $0.00266 |
| Sonnet 5 | $0.00006 | $0.00106 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
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 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Planner Standards
Task Management
- Plan First: Write plan with checkable items before starting.
- Verify Plan: Check in with the user before executing.
- Track Progress: Mark items complete as you go.
- Explain Changes: High-level summary at each step.
- Document Results: Add review section when complete.
- Capture Lessons: Update
.memory/LESSONS.mdafter corrections.
Task Quality
- Tasks must be clear, specific, and actionable.
- Complex tasks must be broken into atomic, trackable subtasks.
- Dependencies between tasks must be explicitly declared.
- Security-related tasks must undergo mandatory review.
- Escalate ambiguous or contradictory tasks for clarification.
Blueprint Check (if configured)
If Blueprint Path is set in .memory/CONFIG.md and the task involves shared
business logic:
- Read the relevant spec(s) in
[BLUEPRINT_PATH]/specs/before planning. - Check
[BLUEPRINT_PATH]/parity/PARITY_MATRIX.mdfor current platform status. - Include in the plan: "Requires Knowledge Bus entry" if the change affects cross-platform contracts.
- Note any spec gaps — if the spec is missing or incomplete, plan a spec update as part of the task.
Skip this section if no blueprint is configured or the task is project-specific.
Change Tracking
- All rule or config changes must be documented in CHANGELOG.md.
- Record source, timestamp, and rationale when modifying shared assets.
- A rollback plan must be defined for every major change.
Subagent Strategy
When a task benefits from fresh context, parallel execution, or isolated scope,
use the subagent-dispatch skill. It provides prompt templates for
implementer, reviewer, and researcher subagents with explicit scope boundaries
and result validation.
When to dispatch:
- Subtasks are independent and can proceed in parallel
- Parallel execution provides meaningful time savings
- Fresh context helps (no accumulated conversation noise)
- Scope of each subtask is clear and self-contained
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 · 60 lines · 30 tokens per session scan A 1ca19d7f9166
task-planner is a skill published in the GitHub repository ahmadulhoq/agentskel (13 stars, last pushed 18d ago), licensed MIT. It adds 30 tokens to every session and 532 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-09-02.
Other skills, from other repositories
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
subagent-delegation
Canonical protocol for delegating GSD work to native Antigravity subagents — when to delegate, how to invoke, workspace isolation modes, and the inline fallback for older IDE versions.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
project-init
Scaffold an unconfigured directory into a configured pi project. Interactive, profile-driven: previews the planned writes, then writes AGENTS.md, .pi/settings.json and prompt files — optionally also a knowledge base, an openspec/ scaffold, and user-global /.pi/agent/settings.json. Use on a bare directory, or when the…