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.
npx agentmods add agents/davila7/claude-code-templates/component-migratorgit clone --depth 1 https://github.com/davila7/claude-code-templatesWhat 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 | $0.00046 | $0.02598 |
| Opus 5 | $0.00023 | $0.01299 |
| Sonnet 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 3d 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.
- 3d 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 (30,476 stars, last pushed 2d ago), licensed MIT. It adds 46 tokens to every session and 2,598 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
config-safety-reviewer
Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.
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.…
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 …
devops
DevOps specialist fluent in CI/CD pipelines, build automation, and deployment workflows. Thinks in reliability, security, and developer experience. Designs GitHub Actions, configures build systems, manages secrets. Use for pipeline configuration, infrastructure automation, and anything involving environments…
claims-auditor
Use this agent once per story at story-final, after validation passes, to verify the orchestrator's completion claims against on-disk artifacts before the story is marked complete. Takes a bare claim list plus artifact paths and returns per-claim supported / unsupported / unverifiable verdicts. It audits the narrator…
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…