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 AlteredCraft/claude-code-plugins --skill task-list-creatorgit clone --depth 1 https://github.com/AlteredCraft/claude-code-pluginsWrote 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/alteredcraft/claude-code-plugins/task-list-creator)<a href="https://agentmods.dev/skills/alteredcraft/claude-code-plugins/task-list-creator"><img src="https://agentmods.dev/badge/skills/alteredcraft/claude-code-plugins/task-list-creator/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/alteredcraft/claude-code-plugins/task-list-creator"><img src="https://agentmods.dev/badge/skills/alteredcraft/claude-code-plugins/task-list-creator.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.00015 | $0.00812 |
| Opus 5.5 | $0.00006 | $0.00325 |
| Sonnet 5.5 | $0.00003 | $0.00162 |
| Haiku 4.5 | $0.00002 | $0.00081 |
Grade A, and why
task-list-creator 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 2mo 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.
You are creating the Task List artifact (todo.md) for an artifact-driven development workflow.
Input Context
You have access to the interrogation context from the conversation—requirements, scope, constraints, and success criteria gathered from the user.
Your Task
Create .artifacts/bld-<project-slug>/todo.md (create the directory if it doesn't exist).
Task Structure
Organize tasks into three phases with hierarchical nesting:
Planning Phase
Research, design decisions, and technical approach tasks that happen before coding.
Implementation Phase
The actual build work. Group related tasks under parent items with subtasks:
- Parent task (e.g., "Implement backend API aggregation service")
- Subtask (e.g., "Integrate multiple weather data sources")
- Subtask (e.g., "Implement data normalization layer")
Verification Phase
Testing, validation, and documentation tasks.
Task Decomposition Principles
-
Phase-first thinking — What research/design must happen before building? What verification happens after?
-
Hierarchical grouping — Group related implementation work under parent tasks. Subtasks should be completable independently but contribute to the parent goal.
-
Atomic subtasks — Each subtask is a single, verifiable unit. Parent tasks complete when all subtasks complete.
-
Include the unsexy work — Error handling, edge cases, fallbacks deserve explicit tasks.
-
Verification is a phase — Not an afterthought. Testing, edge case validation, and documentation are first-class tasks.
For Existing Codebases
If working within an existing codebase:
- Add planning tasks for exploring/understanding current patterns
- Note integration points in implementation subtasks
- Add verification tasks for regression testing
Artifact Structure
---
status: in-progress
created: <timestamp> (ex: 2025-12-09 08:47:19 -0800)
updated: <timestamp> (ex: 2025-12-09 08:49:30 -0800)
project: <project-slug>
description: "<one-line summary>"
---
# <Project Name>
## Planning Phase
- [x] Research X and their capabilities
- [x] Design system architecture and data flow
- [ ] Create implementation plan document
- [ ] Get user approval on technical approach
## Implementation Phase
- [ ] Set up project structure and dependencies
- [ ] Implement backend service
- [ ] Subtask one
- [ ] Subtask two
- [ ] Subtask three
- [ ] Build frontend interface
- [ ] Subtask one
- [ ] Subtask two
- [ ] Add error handling and fallbacks
## Verification Phase
- [ ] Test with multiple scenarios
- [ ] Verify core functionality
- [ ] Test edge cases and error scenarios
- [ ] Create walkthrough documentation
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.
- 2mo ago First seen · 114 lines · 15 tokens per session scan A 48bec98ae9ba
task-list-creator is a skill published in the GitHub repository AlteredCraft/claude-code-plugins (12 stars, last pushed 5mo ago), licensed MIT. It adds 15 tokens to every session and 812 once invoked, about $0.0001 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-30.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…