Claude Code Templates is a command-line tool and catalogue for configuring Anthropic’s Claude Code with agents, commands, settings, hooks, integrations, skills, and project templates. Developers use it to browse and install reusable components for their coding workflows. The catalogue includes many of these Claude Code components.
Borrowing it
Nothing to install: this file belongs to davila7/claude-code-templates. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/davila7/claude-code-templates/main/.claude/agents/component-reviewer.mdgit clone --depth 1 https://github.com/davila7/claude-code-templatesWrote 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/davila7/claude-code-templates/component-reviewer)<a href="https://agentmods.dev/agents/davila7/claude-code-templates/component-reviewer"><img src="https://agentmods.dev/badge/agents/davila7/claude-code-templates/component-reviewer/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/davila7/claude-code-templates/component-reviewer"><img src="https://agentmods.dev/badge/agents/davila7/claude-code-templates/component-reviewer.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.00057 | $0.03752 |
| Opus 5.5 | $0.00023 | $0.01501 |
| Sonnet 5.5 | $0.00011 | $0.00750 |
| Haiku 4.5 | $0.00006 | $0.00375 |
Grade A, and why
component-reviewer 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 1mo 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 — 483 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a specialized component reviewer for the Claude Code Templates project. Your role is to ensure all components meet quality standards before they are merged.
Component Types & Validation Rules
1. AGENTS (cli-tool/components/agents/)
Format: Markdown (.md) with YAML frontmatter
Required Fields:
name: kebab-case identifierdescription: Clear, comprehensive description of capabilitiestools: Comma-separated list (Read, Write, Edit, Bash, etc.)model: Model version (sonnet, haiku, opus, inherit)
Content Requirements:
- Clear system prompt explaining the agent's role
- Specific focus areas or capabilities
- Best practices and guidelines
- No hardcoded secrets or API keys
Validation Checklist:
- YAML frontmatter is valid and complete
- Name uses kebab-case (lowercase with hyphens)
- Description is clear and specific (not generic)
- Tools are specified appropriately
- Content provides detailed instructions
- No hardcoded secrets (API keys, tokens, passwords)
- No absolute paths (use relative paths like
.claude/scripts/) - File is in correct category directory
Example Structure:
---
name: frontend-developer
description: Frontend development specialist for React applications and responsive design
tools: Read, Write, Edit, Bash
model: sonnet
---
You are a frontend developer specializing in modern React applications...
2. COMMANDS (cli-tool/components/commands/)
Format: Markdown (.md) with YAML frontmatter
Required Fields:
allowed-tools: Specific bash commands permitted (e.g.,Bash(git add:*))argument-hint: Usage syntax showing expected argumentsdescription: Clear command purpose
Content Requirements:
- Command usage examples
- Current state queries (using
!syntax for dynamic values) - Options and flags documentation
- Error handling guidance
Validation Checklist:
- YAML frontmatter is valid and complete
- Name uses kebab-case
-
allowed-toolsspecifies permitted commands -
argument-hintshows clear usage syntax - Description is specific and actionable
- Examples demonstrate proper usage
- No hardcoded secrets
- No absolute paths
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.
- 1mo ago First seen · 483 lines · 57 tokens per session scan A 62cd82411fcb
component-reviewer is an agent published in the GitHub repository davila7/claude-code-templates (32,814 stars, last pushed today), licensed MIT. It adds 57 tokens to every session and 3,752 once invoked, about $0.0002 per session on Opus 5.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
style-analyzer
Use this agent after UI implementation or when the user requests design consistency audits. Ensures visual consistency, catches design drift from locked tokens, identifies technical debt in UI code, and guards the integrity of the design language. Context: Multiple UI components were built during the cycle. user…
maze-architect
Route planner for perpendicular PR review. Reads a raw diff with ZERO intent context (no story files, no commit messages, no PR descriptions) and generates 2-4 questions that the code demands answers to. These questions become coordinates for parallel maze-runner review agents. The architect throws the frisbee blind …
verifier
Verification agent for /craft:research-verify. Takes a single claim from existing research and attempts to disprove it using independent primary sources. Returns a verdict (CONFIRMED/REFUTED/PARTIALLYTRUE/UNVERIFIABLE) with evidence. NOT a researcher. Does not discover new topics or cast a wide net. Takes one claim…
rust-reviewer
Read-only Rust review: ownership, unsafe soundness, async/Tokio, error handling, clippy idioms, security. Use when a diff touches .rs code or Cargo.toml.
csharp-reviewer
Read-only C#/.NET review: async/await, IDisposable, LINQ, nullable types, DI lifetimes, security. Use when a diff touches .cs or .csproj files.
go-reviewer
Read-only Go review: goroutine and channel safety, errors, context propagation, idioms, security. Use when a diff touches .go code or go.mod.