todo

A quick command for capturing tasks in a project's Future table, a backlog section in its CLAUDE.md file. It can also list the tasks already recorded there.

In plain words
What is it for?
Use it to list open todos or add a short task such as a bug fix, typo correction, configuration change, or other small piece of work.
Why use it?
It gives small tasks a consistent place to be remembered and checks the project instructions before adding or displaying them.

Command

Install

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.

agentmods
npx agentmods add commands/b33eep/claude-code-setup/todo
Clone the repo
git clone --depth 1 https://github.com/b33eep/claude-code-setup
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 894 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00894
Opus 5 $0.00000 $0.00447
Sonnet 5 $0.00000 $0.00179
Haiku 4.5 $0.00000 $0.00089

Measured 2d ago against content hash 25ceea48c06b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

commands/todo.md · 136 lines

How it starts

The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Todo: Quick Capture for Backlog

Quick capture tool for the Future table. For structured planning, use /design.

/todo = CAPTURE (quick backlog entry)
/design = PLAN (structured design with Record)

Usage

/todo                          # List all todos
/todo Fix typo in README       # Add simple todo
/todo Add notification system  # Complex → hint to use /design

Tasks

Prerequisites

  • If no project CLAUDE.md found: Tell user to run /init-project first
  • If no ### Future section exists: Create it with standard header:
    ### Future
    
    | Todo | Priority | Problem | Solution |
    |------|----------|---------|----------|
    

Without arguments: List todos

  1. Read project CLAUDE.md
  2. Find the ### Future section and its table
  3. Display current todos in table format
  4. If no todos: "No open todos."

With arguments: Add todo

  1. Read project CLAUDE.md

  2. Find the ### Future section and its table

  3. Check for duplicates: If similar todo exists, ask whether to update or add new

  4. Assess complexity:

    Simple (just add to table):

    • Bug fix, typo, small change
    • Config tweak
    • Single file change
    • Clear solution, no design needed

    Complex (hint to use /design):

    • Feature with multiple parts
    • Needs spec or design decisions
    • Architecture decision
    • Multiple sessions likely
    • Unsure how to implement
  5. If simple: Add row to Future table

    | Fix login timeout | Low | Login fails after 30s | Increase timeout |
    
  6. If complex: Do NOT create a Record. Instead:

    This looks like it needs proper design (multiple parts, architecture decision).
    
    Consider using: /design "Add notification system"
    
    Or add as simple reminder anyway? [Yes / No]
    
    • If user says Yes: Add to Future table as reminder
    • If user says No: Suggest running /design
  7. Confirm what was added

Complexity Indicators

Indicator Simple → Use /design
One-liner fix
Single file change
Clear solution
Feature with multiple parts
Needs design decisions
Architecture decision
Multiple sessions likely
Unsure how to implement

Read the full file on GitHub · 136 lines

Changes

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.

  1. 2d ago First seen · 136 lines · 0 tokens per session scan A 25ceea48c06b

Subscribe to this mod's changes

todo is a command published in the GitHub repository b33eep/claude-code-setup (56 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 894 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-30.