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/whats-next)<a href="https://agentmods.dev/commands/glittercowboy/taches-cc-resources/whats-next"><img src="https://agentmods.dev/badge/commands/glittercowboy/taches-cc-resources/whats-next/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/whats-next"><img src="https://agentmods.dev/badge/commands/glittercowboy/taches-cc-resources/whats-next.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.00022 | $0.00903 |
| Opus 5 | $0.00011 | $0.00451 |
| Sonnet 5 | $0.00004 | $0.00181 |
| Haiku 4.5 | $0.00002 | $0.00090 |
Grade A, and why
whats-next 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a comprehensive, detailed handoff document that captures all context from the current conversation. This allows continuing the work in a fresh context with complete precision.
Instructions
PRIORITY: Comprehensive detail and precision over brevity. The goal is to enable someone (or a fresh Claude instance) to pick up exactly where you left off with zero information loss.
Adapt the level of detail to the task type (coding, research, analysis, writing, configuration, etc.) but maintain comprehensive coverage:
-
Original Task: Identify what was initially requested (not new scope or side tasks)
-
Work Completed: Document everything accomplished in detail
- All artifacts created, modified, or analyzed (files, documents, research findings, etc.)
- Specific changes made (code with line numbers, content written, data analyzed, etc.)
- Actions taken (commands run, APIs called, searches performed, tools used, etc.)
- Findings discovered (insights, patterns, answers, data points, etc.)
- Decisions made and the reasoning behind them
-
Work Remaining: Specify exactly what still needs to be done
- Break down remaining work into specific, actionable steps
- Include precise locations, references, or targets (file paths, URLs, data sources, etc.)
- Note dependencies, prerequisites, or ordering requirements
- Specify validation or verification steps needed
-
Attempted Approaches: Capture everything tried, including failures
- Approaches that didn't work and why they failed
- Errors encountered, blockers hit, or limitations discovered
- Dead ends to avoid repeating
- Alternative approaches considered but not pursued
-
Critical Context: Preserve all essential knowledge
- Key decisions and trade-offs considered
- Constraints, requirements, or boundaries
- Important discoveries, gotchas, edge cases, or non-obvious behaviors
- Relevant environment, configuration, or setup details
- Assumptions made that need validation
- References to documentation, sources, or resources consulted
-
Current State: Document the exact current state
- Status of deliverables (complete, in-progress, not started)
- What's committed, saved, or finalized vs. what's temporary or draft
- Any temporary changes, workarounds, or open questions
- Current position in the workflow or process
Write to whats-next.md in the current working directory using the format below.
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 · 109 lines · 22 tokens per session scan A 2721dcb752fb
whats-next is a command published in the GitHub repository glittercowboy/taches-cc-resources (1,977 stars, last pushed 5mo ago), licensed MIT. It adds 22 tokens to every session and 903 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.
Other commands, from other repositories
report
Generate a project analytics report covering code quality, velocity, and health metrics.
debug-pod
Debug a failing or unhealthy Kubernetes pod by analyzing events, logs, and configuration.
explain
Explain a code file, function, or concept in clear, structured language.
env-setup
Set up environment configuration files from templates with validation.
document-all
Auto-document the entire codebase by generating module-level docs, function signatures, and API references.
fix-comments
Address PR review comments by implementing requested changes automatically.