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 commands/evan043/claude-cli-advanced-starter-pack/create-task-list.templategit clone --depth 1 https://github.com/evan043/claude-cli-advanced-starter-packWrote 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/commands/evan043/claude-cli-advanced-starter-pack/create-task-list.template)<a href="https://agentmods.dev/commands/evan043/claude-cli-advanced-starter-pack/create-task-list.template"><img src="https://agentmods.dev/badge/commands/evan043/claude-cli-advanced-starter-pack/create-task-list.template.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.00000 | $0.10995 |
| Opus 5 | $0.00000 | $0.05497 |
| Sonnet 5 | $0.00000 | $0.02199 |
| Haiku 4.5 | $0.00000 | $0.01099 |
Grade A, and why
create-task-list.template scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Task workflow**: Debug with curl → {{testing.e2e.framework}} test → commit after each task How it starts
The opening of the file, as written. The whole thing — 1,312 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Runtime Compatibility
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows:
AskUserQuestion=> ask the user directly in chat.WebSearch/WebFetch=> use available web tools (search_query,open,find) and cite links.Read/Write=> use shell/filesystem tools in this workspace.- Claude-only MCP calls (for example Playwright MCP names) => use available equivalents or clearly state fallback.
- Keep intent and output format identical; only adapt execution mechanics.
description: Create intelligent task list with codebase exploration and clarifying questions type: project complexity: medium model: opus argument-hint: [task or feature description] allowed-tools:
- Read
- Grep
- Glob
- Task
- TaskCreate
- TaskUpdate
- TaskList
- AskUserQuestion
- Write
/create-task-list - Intelligent Task List Generator
Create a comprehensive task list with codebase exploration, clarifying questions, and persistent testing instructions.
QUICK START
/create-task-list fix the login page redirect bug
/create-task-list add dark mode to the settings panel
/create-task-list for issue #123 # Analyze issue, generate tasks
/create-task-list for issue #123 --use-existing-tasks # Use issue's task checklist
/create-task-list
FLAGS & ARGUMENTS
| Argument | Description |
|---|---|
for issue #[N] |
Pull context from GitHub issue #N |
--use-existing-tasks |
Skip task generation, use issue's existing ## Task Checklist |
When for issue #[NUMBER] is specified:
- Fetch issue via
gh issue view [NUMBER] --json number,title,body,labels - Use issue title + body as the task prompt
- Extract labels for context (frontend, backend, P1, etc.)
When --use-existing-tasks is specified:
- Parse existing checklist from
## Task Checklistor## Acceptance Criteria - Skip Step 5 (task generation) - use parsed tasks directly
- Still run full workflow: exploration, testing questions, workflow options
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.
- 4d ago First seen · 1,312 lines · 0 tokens per session scan A 4e68822f72b1
create-task-list.template is a command published in the GitHub repository evan043/claude-cli-advanced-starter-pack (61 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 10,995 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.