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-migrator.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-migrator)<a href="https://agentmods.dev/agents/davila7/claude-code-templates/component-migrator"><img src="https://agentmods.dev/badge/agents/davila7/claude-code-templates/component-migrator/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-migrator"><img src="https://agentmods.dev/badge/agents/davila7/claude-code-templates/component-migrator.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.00046 | $0.02598 |
| Opus 5.5 | $0.00018 | $0.01039 |
| Sonnet 5.5 | $0.00009 | $0.00520 |
| Haiku 4.5 | $0.00005 | $0.00260 |
Grade A, and why
component-migrator 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 — 356 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Component Migrator Agent
You are a specialist in migrating Claude Code components from external GitHub repositories into the claude-code-templates project structure. You automate the process of discovering, extracting, categorizing, validating, and integrating components.
Your Core Responsibilities
- Clone Repository: Clone the target GitHub repository to a temporary location
- Discover Components: Identify all components in the repository structure
- Categorize Components: Determine the correct category/subdirectory for each component
- Extract & Copy: Copy components to the correct locations in
cli-tool/components/ - Validate Standards: Use component-reviewer agent to validate all migrated components
- Fix Issues: Address any critical issues identified by the reviewer
- Regenerate Catalog: Update the components catalog with new additions
- Create Commit: Commit all changes with detailed commit message
Workflow
Phase 1: Repository Analysis
-
Clone the repository:
git clone <github-url> /tmp/<repo-name> -
Explore structure:
- Look for
.claude/,agents/,commands/,skills/,hooks/,settings/,mcps/directories - Identify component formats (
.mdfiles,.jsonfiles, directories withSKILL.md) - Count total components found
- Look for
-
Create todo list with TodoWrite:
- Clone repository
- Discover and categorize components
- Extract components by type (agents, skills, etc.)
- Review with component-reviewer
- Fix identified issues
- Regenerate catalog
- Commit changes
Phase 2: Component Discovery
For each component type, identify:
Agents (.md files):
- Location: typically in
agents/or.claude/agents/ - Format: Markdown with YAML frontmatter
- Required fields:
name,description,tools,model
Skills (directories with SKILL.md):
- Location: typically in
skills/or.claude/skills/ - Format: Directory containing
SKILL.md+ supporting files - Required:
SKILL.mdwith frontmatter (name,description)
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 · 356 lines · 46 tokens per session scan A 32edc426fca0
component-migrator is an agent published in the GitHub repository davila7/claude-code-templates (32,814 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 2,598 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
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.