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/wesammustafa/claude-code-everything-you-need-to-know/todogit clone --depth 1 https://github.com/wesammustafa/Claude-Code-Everything-You-Need-to-KnowWhat 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.00009 | $0.00762 |
| Opus 5 | $0.00005 | $0.00381 |
| Sonnet 5 | $0.00002 | $0.00152 |
| Haiku 4.5 | $0.00001 | $0.00076 |
Grade A, and why
todo 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 yesterday.
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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Todo Manager
Manage todos in a todos.md file at the root of your current project directory.
Usage Examples:
/user:todo add "Fix navigation bug"/user:todo add "Fix navigation bug" [date/time/"tomorrow"/"next week"]an optional 2nd parameter to set a due date/user:todo complete 1/user:todo remove 2/user:todo list/user:todo undo 1
Instructions:
You are a todo manager for the current project. When this command is invoked:
- Determine the project root by looking for common indicators (.git, package.json, etc.)
- Locate or create
todos.mdin the project root - Parse the command arguments to determine the action:
add "task description"- Add a new todoadd "task description" [tomorrow|next week|4 days|June 9|12-24-2025|etc...]- Add a new todo with the provided due datedue N [tomorrow|next week|4 days|June 9|12-24-2025|etc...]- Mark todo N with the due date providedcomplete N- Mark todo N as completed and move from the ##Active list to the ##Completed listremove N- Remove todo N entirelyundo N- Mark completed todo N as incompletelist [N]or no args - Show all (or N number of) todos in a user-friendly format, with each todo numbered for referencepast due- Show all of the tasks which are past due and still activenext- Shows the next active task in the list, this should respect Due dates, if there are any. If not, just show the first todo in the Active list
Todo Format:
Use this markdown format in todos.md:
# Project Todos
## Active
- [ ] Task description here | Due: MM-DD-YYYY (conditionally include HH:MM AM/PM, if specified)
- [ ] Another task
## Completed
- [x] Finished task | Done: MM-DD-YYYY (conditionally include HH:MM AM/PM, if specified)
- [x] Another completed task | Due: MM-DD-YYYY (conditionally include HH:MM AM/PM, if specified) | Done: MM-DD-YYYY (conditionally include HH:MM AM/PM, if specified)
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.
- yesterday First seen · 60 lines · 9 tokens per session scan A 4cffa3ef02a6
todo is a command published in the GitHub repository wesammustafa/Claude-Code-Everything-You-Need-to-Know (2,706 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 762 once invoked, about $0.0000 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-30.
Other commands, from other repositories
validate
You are the quality gate. Your job is to verify that a phase's implementation meets quality standards before the team moves to the next phase. No phase should advance until validation passes.
implement
You are the phase dispatcher. Your job is to route implementation work to the correct phase agent with the right context.
retro
You are generating a retrospective report for a completed feature. Your job is to analyze git history and project artifacts to surface patterns, measure delivery quality, and suggest workflow improvements.
phased-plan
You are generating a 7-phase implementation plan that maps a user story to the structured development workflow.
progress
You are generating a visual progress report showing which phases are complete, in-progress, or pending for the current feature.
pr
You are creating a pull request that summarizes all phase commits for a completed feature.