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/walterra/claude-code-helpersWrote 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/walterra/claude-code-helpers/todo)<a href="https://agentmods.dev/commands/walterra/claude-code-helpers/todo"><img src="https://agentmods.dev/badge/commands/walterra/claude-code-helpers/todo/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/commands/walterra/claude-code-helpers/todo"><img src="https://agentmods.dev/badge/commands/walterra/claude-code-helpers/todo.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.00000 | $0.03389 |
| Opus 5.5 | $0.00000 | $0.01356 |
| Sonnet 5.5 | $0.00000 | $0.00678 |
| Haiku 4.5 | $0.00000 | $0.00339 |
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 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 — 343 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Todo Implementation Program
Structured workflow for implementing items from spec/todo.md. Work isolation in spec/todos/work/, completion tracking in spec/todos/done/. Enables concurrent work.
Overall guidance:
- CRITICAL: Follow all steps in the workflow! Do not miss executing any steps!
- CRITICAL: When refactoring, never assume that your code changes fix a problem without testing. Refactor using this loop: define goal -> code change -> test (use all available tools: logs/playwright mcp/screenshots etc.) -> if your testing doesn't satisfy the goal, move back to code change, repeat until done. if you're stuck, web research for solutions.
- Never mark off checkbox items as done when there are not fully completed or fixed!
- NEVER COMMIT OR PUSH: Agent must NEVER run git commit or git push commands. Only the USER commits/pushes changes.
Inputs
spec/todo.md - User's todo list (free form, any format):
- Add dark mode toggle to settings
- Should persist across sessions
- Use system preference as default
Fix memory leak in WebSocket handler
See issue #123
spec/project-description.md - Project context and commands (auto-generated, user-editable):
CRITICAL: always read spec/project-description.md for context.
# Project: Claude Code notifications
Shows system notifications when Claude Code sessions need user input.
TypeScript/Swift CLI tool with macOS daemon.
## Features
- System tray notifications
- Session monitoring
- macOS integration
## Commands
- **Check**: `npm run check`
- **Test**: `npm test`
- **Build**: `npm run build`
## Structure
src/cli.ts # CLI entry
src/mac/daemon.swift # Menu bar app
src/notifications.ts # Core logic
State
CRITICAL: Always keep the work items in sync in task.md in sync with your todos. Task completion requires ALL success criteria to be met.
ABSOLUTE RULE FOR TASK COMPLETION:
- NEVER mark any task item as [x] completed unless it is ABSOLUTELY, VERIFIABLY complete
- If ANY part of a task fails, produces errors, or doesn't work as specified, it MUST remain [ ] incomplete
- "Implemented" ≠ "Working" - only mark complete when functionality is verified working
- If you say "SUCCESS CRITERIA NOT MET" anywhere, NO related items can be marked [x] completed
- When in doubt, keep items unchecked [ ] - it's better to under-report progress than over-report
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 · 343 lines · 0 tokens per session scan A 88bb207536e2
todo is a command published in the GitHub repository walterra/claude-code-helpers (5 stars, last pushed 1y ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 3,389 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-08-31.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
sync-linear
Sync current work with Linear ticket status.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.