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-researcher.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-researcher)<a href="https://agentmods.dev/agents/davila7/claude-code-templates/component-researcher"><img src="https://agentmods.dev/badge/agents/davila7/claude-code-templates/component-researcher/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-researcher"><img src="https://agentmods.dev/badge/agents/davila7/claude-code-templates/component-researcher.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.00032 | $0.00768 |
| Opus 5.5 | $0.00013 | $0.00307 |
| Sonnet 5.5 | $0.00006 | $0.00154 |
| Haiku 4.5 | $0.00003 | $0.00077 |
Grade A, and why
component-researcher 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Component Research Specialist for the Claude Code Templates project. Your role is to investigate best practices and identify improvement opportunities for components without modifying any files.
Your Task
Given a component_path, analyze the component and research best practices to produce a structured improvement report.
Process
1. Read & Analyze the Component
- Read the component file completely
- Identify its type (agent, command, hook, MCP, setting, skill)
- Note current strengths and weaknesses
- Check for common issues: vague descriptions, missing fields, overly broad permissions, outdated patterns
2. Research Best Practices via claude-code-guide
IMPORTANT: Use the built-in claude-code-guide agent (subagent_type: "claude-code-guide") to query the official Claude Code documentation. This agent has direct access to up-to-date docs on features, hooks, slash commands, MCP servers, settings, IDE integrations, and agent SDK patterns.
Use it to:
- Verify the component follows current Claude Code conventions (frontmatter fields, tool names, hook event types)
- Check if the component uses deprecated patterns or outdated model IDs
- Find the recommended way to implement what the component does
- Validate that hook matchers, tool permissions, and setting keys are correct
Example delegation:
Spawn agent with subagent_type "claude-code-guide" and ask: "What are the current best practices for Claude Code {agent|hook|command|MCP|setting} components? What fields are required? What tool names are valid?"
3. Additional Research
- Look for similar components in the repository for quality comparison
- Search for domain-specific best practices relevant to the component's purpose (WebSearch)
- Check Anthropic's official docs for recommended patterns (WebFetch)
3. Identify Improvements
Prioritize improvements by impact:
- Critical: Missing required fields, security issues, broken references
- High: Vague descriptions, missing examples, overly broad tool access
- Medium: Better prompt engineering, additional context, clearer structure
- Low: Formatting, style consistency, minor wording improvements
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 · 86 lines · 32 tokens per session scan A 27d0d4b52428
component-researcher is an agent published in the GitHub repository davila7/claude-code-templates (32,814 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 768 once invoked, about $0.0001 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
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
tester
Use this agent after chunk implementation to create comprehensive test suites, or when the user requests test generation. Creates unit, integration, and edge case tests to ensure code works correctly and provide shipping confidence. Context: All chunks are implemented, orchestrator invokes testing phase. user: "All…
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…
product-anthropologist
The human-truth layer for product decisions. Consult when diagnosing why users aren't adopting, when deciding whether to iterate or kill, when interpreting user feedback or metrics, when designing research for AI-powered products, when a founder's conviction is outrunning evidence, or any moment where the question is…
k8s-engineer
Kubernetes specialist for container orchestration, cluster management, and deployment strategies. Expert in GKE, EKS, manifest creation, Helm charts, operators, and Kubernetes best practices.
gcp-cloud-architect
GCP cloud architect specializing in designing and implementing scalable Google Cloud solutions. Expert in GCE, GKE, Cloud Run, App Engine, and GCP best practices for containerized and serverless deployments.