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 hamzaPixl/pixl-ai --skill task-plangit clone --depth 1 https://github.com/hamzaPixl/pixl-aiWrote 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/hamzapixl/pixl-ai/task-plan)<a href="https://agentmods.dev/skills/hamzapixl/pixl-ai/task-plan"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/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/hamzapixl/pixl-ai/task-plan"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/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.00101 | $0.01188 |
| Opus 5.5 | $0.00040 | $0.00475 |
| Sonnet 5.5 | $0.00020 | $0.00238 |
| Haiku 4.5 | $0.00010 | $0.00119 |
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 1mo 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
This skill creates structured task plans for implementation work. Given a feature, project, or change request, it analyzes the scope, decomposes work into atomic tasks, adds acceptance criteria and dependency relationships, and outputs a complete execution plan.
Why vertical slices over horizontal layers: Vertical slices (each delivering user-visible value) provide faster feedback than horizontal layers (build all DB first, then all API, then all UI). If a vertical slice fails, you learn early; if a horizontal layer fails, you've built foundations for features that may never ship.
Required References
Before starting, read references/methodology/vertical-slice.md for vertical slice decomposition patterns.
Step 0: Input Parsing (conditional)
If the argument appears to be a file path (contains / or .md or .txt or .pdf):
- Read the file using the Read tool
- Extract requirements, user stories, and acceptance criteria from the document
- Summarize the key features and scope before proceeding to Step 1
If the argument appears to be a URL:
- Fetch the URL content using WebFetch
- Extract requirements from the page content
- Summarize before proceeding
Otherwise, treat the argument as a direct feature description and proceed to Step 0.5 (if applicable) or Step 1.
Step 0.5: Drift-Aware Replanning (conditional)
If .context/spec/coverage-<latest>.json exists (produced by /spec-review):
- Load coverage report: Read the most recent
coverage-*.jsonfrom.context/spec/ - Load existing task plan: Read
.context/task-state.jsonif it exists - Cross-reference: Match coverage results against existing tasks:
missingrequirements with no corresponding task → new tasks neededaddeddrift entries (fromdrift-log.jsonl) → new tasks neededremoveddrift entries → existing tasks may be irrelevantreprioritizeddrift entries → existing tasks may need reordering
- Present adaptation summary to the user via AskUserQuestion:
- New tasks to add (from missing/added requirements)
- Tasks to remove or deprioritize (from removed requirements)
- Tasks to reorder (from reprioritized requirements)
- User confirms before changes are applied
- Merge into existing plan: Update
.context/task-state.jsonwith adaptations, then proceed to Step 1 for any new work
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.
- 1mo ago First seen · 114 lines · 101 tokens per session scan A 96eae75789ef
task-plan is a skill published in the GitHub repository hamzaPixl/pixl-ai (2 stars, last pushed 6mo ago), licensed MIT. It adds 101 tokens to every session and 1,188 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.