Borrowing it
Nothing to install: this file belongs to hlalljie/agent-workflow-presets. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/hlalljie/agent-workflow-presets/main/.cursor/skills/create-task-list/SKILL.mdgit 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/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/hlalljie/agent-workflow-presets/create-task-list"><img src="https://agentmods.dev/badge/skills/hlalljie/agent-workflow-presets/create-task-list.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.00033 | $0.00806 |
| Opus 5.5 | $0.00013 | $0.00322 |
| Sonnet 5.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 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 — 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.
- 1mo 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 20d ago), licensed MIT. It adds 33 tokens to every session and 806 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-31.
Other skills, from other repositories
work-on-ticket
Fetches Jira ticket details, creates an appropriately named branch, and initiates the task planning workflow. Use when the user says "work on [TICKETID]" or similar phrases.
cast-plan
Turn a request into a plan the team can review before code exists. Explores the codebase, searches prior sessions and recorded decisions for earlier attempts, interviews the user on the open questions, then writes a codecast plan with tasks and dependencies ready for orchestrate. Use when work has several parts, when…
cast-org
Talk through the organization of agents and people around this work with the person, in this session: who reports to whom, what each role looks after, where their sessions go. Reads what the code and the sessions say before it trusts a plan or a task, asks what the records cannot settle, and posts each agreed change…
cast-handoff
Package the current work so the next session or a teammate can continue without reading this thread. Writes the decisions, the direction, what is verified, open questions and ordered next steps as a shared doc, pins the state, and optionally forks, spawns or hands the work to a session. Use before stopping, before a…
cast-loop
Run an autonomous loop that works through a queue of tasks one fresh session at a time, with verification as the gate and a human decision at merge. Sets up a recurring trigger that spawns a session per ready task, a precheck that spends nothing when the queue is empty, and the rules each run follows. Use for a…
cast-conflicts
Before editing or fanning out work, find the live sessions on this repository that are changing the same files, show what they changed, and warn them. Use before starting a task that touches shared files, before spawning workers, or when asked who else is working on this.