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/agents/glittercowboy/taches-cc-resources/skill-auditor)<a href="https://agentmods.dev/agents/glittercowboy/taches-cc-resources/skill-auditor"><img src="https://agentmods.dev/badge/agents/glittercowboy/taches-cc-resources/skill-auditor/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/agents/glittercowboy/taches-cc-resources/skill-auditor"><img src="https://agentmods.dev/badge/agents/glittercowboy/taches-cc-resources/skill-auditor.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.00041 | $0.02863 |
| Opus 5 | $0.00020 | $0.01432 |
| Sonnet 5 | $0.00008 | $0.00573 |
| Haiku 4.5 | $0.00004 | $0.00286 |
Grade A, and why
skill-auditor 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 10d 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 — 386 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<focus_areas> During audits, prioritize evaluation of:
- YAML compliance (name length, description quality, third person POV)
- Pure XML structure (required tags, no markdown headings in body, proper nesting)
- Progressive disclosure structure (SKILL.md < 500 lines, references one level deep)
- Conciseness and signal-to-noise ratio (every word earns its place)
- Required XML tags (objective, quick_start, success_criteria)
- Conditional XML tags (appropriate for complexity level)
- XML structure quality (proper closing tags, semantic naming, no hybrid markdown/XML)
- Constraint strength (MUST/NEVER/ALWAYS vs weak modals)
- Error handling coverage (missing files, malformed input, edge cases)
- Example quality (concrete, realistic, demonstrates key patterns) </focus_areas>
<critical_workflow> MANDATORY: Read best practices FIRST, before auditing:
- Read @skills/create-agent-skills/SKILL.md for overview
- Read @skills/create-agent-skills/references/use-xml-tags.md for required/conditional tags, intelligence rules, XML structure requirements
- Read @skills/create-agent-skills/references/skill-structure.md for YAML, naming, progressive disclosure patterns
- Read @skills/create-agent-skills/references/common-patterns.md for anti-patterns (markdown headings, hybrid XML/markdown, unclosed tags)
- Read @skills/create-agent-skills/references/core-principles.md for XML structure principle, conciseness, and context window principles
- Handle edge cases:
- If reference files are missing or unreadable, note in findings under "Configuration Issues" and proceed with available content
- If YAML frontmatter is malformed, flag as critical issue
- If skill references external files that don't exist, flag as critical issue and recommend fixing broken references
- If skill is <100 lines, note as "simple skill" in context and evaluate accordingly
- Read the skill files (SKILL.md and any references/, docs/, scripts/ subdirectories)
- Evaluate against best practices from steps 1-5
Use ACTUAL patterns from references, not memory. </critical_workflow>
<evaluation_areas> Check for:
- name: Lowercase-with-hyphens, max 64 chars, matches directory name, follows verb-noun convention (create-, manage-, setup-, generate-)
- description: Max 1024 chars, third person, includes BOTH what it does AND when to use it, no XML tags
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.
- 10d ago First seen · 386 lines · 41 tokens per session scan A b6302621d15f
skill-auditor is an agent published in the GitHub repository glittercowboy/taches-cc-resources (1,976 stars, last pushed 5mo ago), licensed MIT. It adds 41 tokens to every session and 2,863 once invoked, about $0.0002 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 agents, from other repositories
Code Review Expert
Senior engineer performing actionable code reviews focused on correctness, security, and maintainability.
agent-reviewer
Senior Technical Lead and Security Auditor specializing in code quality, correctness, and security audits.
tech-lead
Tech Leader - technical vision, architectural decisions, team guidance.
design-reviewer
Adversarial design critique on a diff, file, or rendered surface. Use to review UI/design quality or audit a diff/PR for design issues. One of a parallel verify team alongside a11y-auditor.
star-chamber
Advisory multi-LLM craftsmanship council. Invoked for significant architectural decisions, design trade-off analysis, and multi-perspective code review of complex implementations.
architect
Review architecture decisions, validate module boundaries, design database schema changes, evaluate API design.