add-to-todos

add-to-todos is a command for Claude Code from glittercowboy/taches-cc-resources. It costs 12 tokens per session (707 once invoked), scanned A, original, MIT.

A command for adding a task to a file named TO-DOS.md, including useful context from the conversation. It checks the file for similar tasks before adding anything.

In plain words
What is it for?
Use it to record a new task, include relevant files and technical details, and decide whether to skip, replace, or keep a duplicate task.
Why use it?
It reduces the chance of losing a task or creating duplicate entries. When a similar task exists, it asks how you want to handle it.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the taches-cc-resources plugin — 12 skills, 19 commands, 3 agents shipped together

Good fit Use it to record a new task, include relevant files and technical details, and decide whether to skip, replace, or keep a duplicate task.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/glittercowboy/taches-cc-resources/add-to-todos
About the project

TÂCHES Claude Code Resources is a collection of custom commands, skills, and agents that structure Claude Code workflows such as planning, debugging, automation, and subagent creation. It is intended for developers who use Claude Code for real software projects. The catalogue entries are examples of the resources included in the collection.

glittercowboy/taches-cc-resources · 1,977 stars · on GitHub · youtube.com

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.

Clone the repo
git clone --depth 1 https://github.com/glittercowboy/taches-cc-resources

Made for: Claude Code.

Or install taches-cc-resources, the plugin that ships this one along with the rest of its 12 skills, 19 commands, 3 agents.

Wrote 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.

agentmods badge for add-to-todos

README.md
[![agentmods](https://agentmods.dev/badge/commands/glittercowboy/taches-cc-resources/add-to-todos/github.svg)](https://agentmods.dev/commands/glittercowboy/taches-cc-resources/add-to-todos)
Your own site
<a href="https://agentmods.dev/commands/glittercowboy/taches-cc-resources/add-to-todos"><img src="https://agentmods.dev/badge/commands/glittercowboy/taches-cc-resources/add-to-todos/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.

agentmods 80×15 button for add-to-todos

Your own site · 80×15
<a href="https://agentmods.dev/commands/glittercowboy/taches-cc-resources/add-to-todos"><img src="https://agentmods.dev/badge/commands/glittercowboy/taches-cc-resources/add-to-todos.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 707 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00012 $0.00707
Opus 5 $0.00006 $0.00353
Sonnet 5 $0.00002 $0.00141
Haiku 4.5 $0.00001 $0.00071

Measured 12d ago against content hash de3b579683dd, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

add-to-todos 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 12d 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/add-to-todos.md · 57 lines

How it starts

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

Add Todo Item

Context

  • Current timestamp: !date "+%Y-%m-%d %H:%M"

Instructions

  1. Read TO-DOS.md in the working directory (create with Write tool if it doesn't exist)

  2. Check for duplicates:

    • Extract key concept/action from the new todo
    • Search existing todos for similar titles or overlapping scope
    • If found, ask user: "A similar todo already exists: [title]. Would you like to:\n\n1. Skip adding (keep existing)\n2. Replace existing with new version\n3. Add anyway as separate item\n\nReply with the number of your choice."
    • Wait for user response before proceeding
  3. Extract todo content:

    • With $ARGUMENTS: Use as the focus/title for the todo and context heading
    • Without $ARGUMENTS: Analyze recent conversation to extract:
      • Specific problem or task discussed
      • Relevant file paths that need attention
      • Technical details (line numbers, error messages, conflicting specifications)
      • Root cause if identified
  4. Append new section to bottom of file:

    • Heading: ## Brief Context Title - YYYY-MM-DD HH:MM (3-8 word title, current timestamp)
    • Todo format: - **[Action verb] [Component]** - [Brief description]. **Problem:** [What's wrong/why needed]. **Files:** [Comma-separated paths with line numbers]. **Solution:** [Approach hints or constraints, if applicable].
    • Required fields: Problem and Files (with line numbers like path/to/file.ts:123-145)
    • Optional field: Solution
    • Make each section self-contained for future Claude to understand weeks later
    • Use simple list items (not checkboxes) - todos are removed when work begins
  5. Confirm and offer to continue with original work:

    • Identify what the user was working on before /add-to-todos was called
    • Confirm the todo was saved: "✓ Saved to todos."
    • Ask if they want to continue with the original work: "Would you like to continue with [original task]?"
    • Wait for user response

Format Example

## Add Todo Command Improvements - 2025-11-15 14:23

- **Add structured format to add-to-todos** - Standardize todo entries with Problem/Files/Solution pattern. **Problem:** Current todos lack consistent structure, making it hard for Claude to have enough context when revisiting tasks later. **Files:** `commands/add-to-todos.md:22-29`. **Solution:** Use inline bold labels with required Problem and Files fields, optional Solution field.

- **Create check-todos command** - Build companion command to list and select todos. **Problem:** Need workflow to review outstanding todos and load context for selected item. **Files:** `commands/check-todos.md` (new), `TO-DOS.md` (reads from). **Solution:** Parse markdown list, display numbered list, accept selection to load full context and remove item.

Read the full file on GitHub · 57 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. 12d ago First seen · 57 lines · 12 tokens per session scan A de3b579683dd

Subscribe to this mod's changes

add-to-todos is a command published in the GitHub repository glittercowboy/taches-cc-resources (1,977 stars, last pushed 5mo ago), licensed MIT. It adds 12 tokens to every session and 707 once invoked, about $0.0001 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.