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.
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/glittercowboy/taches-cc-resourcesWrote 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/glittercowboy/taches-cc-resources/check-todos)<a href="https://agentmods.dev/commands/glittercowboy/taches-cc-resources/check-todos"><img src="https://agentmods.dev/badge/commands/glittercowboy/taches-cc-resources/check-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.
<a href="https://agentmods.dev/commands/glittercowboy/taches-cc-resources/check-todos"><img src="https://agentmods.dev/badge/commands/glittercowboy/taches-cc-resources/check-todos.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.00009 | $0.00628 |
| Opus 5 | $0.00005 | $0.00314 |
| Sonnet 5 | $0.00002 | $0.00126 |
| Haiku 4.5 | $0.00001 | $0.00063 |
Grade A, and why
check-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 13d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check Todos
Instructions
-
Read TO-DOS.md in the working directory (if doesn't exist, say "No outstanding todos" and exit)
-
Parse and display todos:
- Extract all list items starting with
- **(active todos) - If none exist, say "No outstanding todos" and exit
- Display compact numbered list showing:
- Number (for selection)
- Bold title only (part between
**markers) - Date from h2 heading above it
- Prompt: "Reply with the number of the todo you'd like to work on."
- Wait for user to reply with a number
- Extract all list items starting with
-
Load full context for selected todo:
- Display complete line with all fields (Problem, Files, Solution)
- Display h2 heading (topic + date) for additional context
- Read and briefly summarize relevant files mentioned
-
Check for established workflows:
- Read CLAUDE.md (if exists) to understand project-specific workflows and rules
- Look for
.claude/skills/directory - Match file paths in todo to domain patterns (
plugins/→ plugin workflow,mcp-servers/→ MCP workflow) - Check CLAUDE.md for explicit workflow requirements for this type of work
-
Present action options to user:
- If matching skill/workflow found: "This looks like [domain] work. Would you like to:\n\n1. Invoke [skill-name] skill and start\n2. Work on it directly\n3. Brainstorm approach first\n4. Put it back and browse other todos\n\nReply with the number of your choice."
- If no workflow match: "Would you like to:\n\n1. Start working on it\n2. Brainstorm approach first\n3. Put it back and browse other todos\n\nReply with the number of your choice."
- Wait for user response
-
Handle user choice:
- Option "Invoke skill" or "Start working": Remove todo from TO-DOS.md (and h2 heading if section becomes empty), then begin work (invoke skill if applicable, or proceed directly)
- Option "Brainstorm approach": Keep todo in file, invoke
/brainstormwith the todo description as argument - Option "Put it back": Keep todo in file, return to step 2 to display the full list again
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.
- 13d ago First seen · 57 lines · 9 tokens per session scan A 5df8e8016751
check-todos is a command published in the GitHub repository glittercowboy/taches-cc-resources (1,977 stars, last pushed 5mo ago), licensed MIT. It adds 9 tokens to every session and 628 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
organize
Sort, group, and clean up import statements across the project.
t00-compact
A command that switches replies into an extremely short mode, removing filler and keeping only conclusions, code, numbers, errors, and pending decisions.
report
Generate a project analytics report covering code quality, velocity, and health metrics.
explain
Explain a code file, function, or concept in clear, structured language.
document-all
Auto-document the entire codebase by generating module-level docs, function signatures, and API references.
write-post
Write a technical blog post with a clear structure, code examples, and actionable takeaways.