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.
git 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/todo.template)<a href="https://agentmods.dev/commands/evan043/claude-cli-advanced-starter-pack/todo.template"><img src="https://agentmods.dev/badge/commands/evan043/claude-cli-advanced-starter-pack/todo.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.1 | $0.00000 | $0.02764 |
| Opus 5 | $0.00000 | $0.01382 |
| Sonnet 5 | $0.00000 | $0.00553 |
| Haiku 4.5 | $0.00000 | $0.00276 |
Grade A, and why
todo.template 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 3d 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 — 345 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: View, navigate, and work on todo items with AI-powered intent routing type: utility complexity: medium model: sonnet argument-hint: "[list|work|complete|delete] [item-id]" allowed-tools:
- Read
- Write
- Grep
- Glob
- Task
- AskUserQuestion
- Bash
- Skill
/todo - Smart Todo Manager
View, navigate, and work on your todo items. AI-powered intent detection suggests the best workflow for each item.
QUICK START
/todo # Show interactive menu
/todo list # List all todos
/todo work a1b2c3d4 # Start working on item by ID
/todo complete a1b2c3d4 # Mark item as completed
/todo delete a1b2c3d4 # Delete an item
EXECUTION FLOW
Step 1: Read Todos
Read .claude/todos.json. If file doesn't exist, display:
No todos found. Add one with /todo-add
And stop execution.
Step 2: Parse Arguments
| Argument | Action |
|---|---|
| (none) | Show interactive menu |
list |
Show all todos with status indicators |
work [id] |
Start "Work on item" flow |
complete [id] |
Mark item as completed |
delete [id] |
Delete item (with confirmation) |
Step 3: Interactive Menu (Default)
If no arguments provided, show the todo list and menu:
╔═══════════════════════════════════════════════════╗
║ Todo List (5 items) ║
╠═══════════════════════════════════════════════════╣
║ ║
║ PENDING (3) ║
║ ○ [a1b2] Fix login redirect on mobile ║
║ ○ [c3d4] Add dark mode settings toggle ║
║ ○ [e5f6] Refactor auth middleware JWT ★ high ║
║ ║
║ IN PROGRESS (1) ║
║ ◉ [g7h8] Build user dashboard charts ║
║ ║
║ COMPLETED (1) ║
║ ✓ [i9j0] Setup CI/CD pipeline ║
║ ║
╚═══════════════════════════════════════════════════╝
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.
- 3d ago First seen · 345 lines · 0 tokens per session scan A 3fd41ac20fde
todo.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 2,764 tokens. 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 commands, from other repositories
suggest-automation
A command that reviews recent Git commits and project instructions to find work patterns that happen repeatedly.
evolve
Cluster related instincts into skills, commands, or agents.
instinct-import
Import instincts from teammates, Skill Creator, or other sources.
instinct-export
Export instincts for sharing with teammates or other projects.
context-stats
Display context window usage and token statistics.
init-project
Initialize project with CLAUDE.md template - adaptive detection for new or existing projects.