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/hlalljie/agent-workflow-presets/create-task-listnpx skills add hlalljie/agent-workflow-presets --skill create-task-listgit clone --depth 1 https://github.com/hlalljie/agent-workflow-presetsWrote 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/hlalljie/agent-workflow-presets/create-task-list)<a href="https://agentmods.dev/skills/hlalljie/agent-workflow-presets/create-task-list"><img src="https://agentmods.dev/badge/skills/hlalljie/agent-workflow-presets/create-task-list.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.00033 | $0.00806 |
| Opus 5 | $0.00016 | $0.00403 |
| Sonnet 5 | $0.00007 | $0.00161 |
| Haiku 4.5 | $0.00003 | $0.00081 |
Grade A, and why
create-task-list 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create task list
When to use
When a plan phase is ready to be worked on and needs concrete implementation steps.
Process
- Read the phase from the plan (the phase description and its details are the source of truth).
- Read linked research and resolved open questions referenced in the phase.
- Check conversation for context not yet written down.
- If information is missing: ask the user for quick things, create an open question if it needs research.
- Write the task list.
Format
The phase description from the plan goes at the top for context. Then tasks with optional subtasks.
# Tasks: <phase name>
<phase description from plan, copied or paraphrased>
### Task 1: Task name
- [ ] Action item
- [ ] Action item
### Task 2: Task name
- [ ] Action item
- [ ] Action item
### Task 3: Larger task name
- [ ] Subtask a
- [ ] Subtask b
- [ ] Subtask c
Writing good tasks
Each task is a concrete action that can be implemented, tested, and verified in one working session. The person doing the task (human or agent) should be able to see the change visually or run tests against it without a large QA burden.
Checklist lines (- [ ])
-
Start every item with an imperative (Write, Add, Build, Run, Verify, Get approval, …). Do not use label-only lines.
-
If a human must approve before more work: name project owner. Do not use you (ambiguous for agents).
-
Say workflow/meta once at the top of the file when needed; do not repeat the same explanation in every task Note.
-
Optional Note under a task title: slice-only facts (ids, scope). Defer domain specifics to linked product docs or the "write dataflow" step—not long Note blocks.
-
Testable in isolation: after completing a task you should be able to verify it works without needing other incomplete tasks.
-
Easy to verify: either visually checkable or has a small focused test. Avoid tasks where QA requires checking many things at once.
-
Easy to fix: if something breaks, the scope is small enough to find and fix quickly.
-
One task at a time. Move to next only when current is done and verified. See
workflow.mdc"Executing tasks" for cadence rules. -
If a phase has low verification burden (e.g. pure setup), add
batchable: truebelow the phase description to allow batching. Default is one-at-a-time.
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 · 81 lines · 33 tokens per session scan A 2b510b5d42fa
create-task-list is a skill published in the GitHub repository hlalljie/agent-workflow-presets (2 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 806 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
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
nft-standards
Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset systems.
cost-optimization
Optimize cloud costs across AWS, Azure, GCP, and OCI through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies.
istio-traffic-management
Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilience patterns.
postgresql-table-design
Use this skill when designing or reviewing a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features.
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.