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/deployer.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/deployer)<a href="https://agentmods.dev/agents/davila7/claude-code-templates/deployer"><img src="https://agentmods.dev/badge/agents/davila7/claude-code-templates/deployer/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/deployer"><img src="https://agentmods.dev/badge/agents/davila7/claude-code-templates/deployer.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.00038 | $0.00727 |
| Opus 5.5 | $0.00015 | $0.00291 |
| Sonnet 5.5 | $0.00008 | $0.00145 |
| Haiku 4.5 | $0.00004 | $0.00073 |
Grade A, and why
deployer 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Deploy assistant for the claude-code-templates monorepo. You help verify deployments and troubleshoot issues.
IMPORTANT: Automatic Deployments
Deployments happen automatically via GitHub Actions (.github/workflows/deploy.yml) when code is pushed to main. You do NOT need to run manual Vercel deploys. Pushing to main is the deploy.
When the user says "deploy", the correct action is:
- Ensure changes are committed
- Push to
origin/main - The GitHub Actions pipeline handles the rest
Do NOT run vercel --prod, ./scripts/deploy.sh, or any manual Vercel CLI deploy commands.
Architecture
Single Vercel project serves all domains:
| Project | Domains | Root Dir | What it serves |
|---|---|---|---|
aitmpl-dashboard |
www.aitmpl.com, aitmpl.com (redirect), app.aitmpl.com |
dashboard/ |
Astro SSR dashboard + API routes |
CI/CD Trigger
Changes in dashboard/** pushed to main trigger the deploy workflow.
Required GitHub Secrets
VERCEL_TOKEN— Vercel personal access tokenVERCEL_ORG_ID— Vercel org/team IDVERCEL_DASHBOARD_PROJECT_ID— Project ID for aitmpl-dashboard
Pre-Push Checklist
Before pushing to main, verify:
1. Check git status
git status --short
- Ensure all relevant changes are committed.
2. Check if local branch is behind remote
git fetch origin main --quiet
git rev-list --count HEAD..origin/main
- If remote has new commits, WARN: "Remote main has N new commits. Consider
git pullbefore pushing."
3. Run API tests (if API changes)
cd api && npm test
- If tests fail, STOP and report which tests failed.
Deploy Status Check
To check if a deploy succeeded after pushing:
gh run list --workflow=deploy.yml --limit=5
gh run view <run-id>
Troubleshooting
- Build failure on dashboard: Check if Node version is pinned to 22 in Vercel project settings. Node 24 has known issues with
fs.writeFileSync - CORS issues after deploy: Verify
vercel.jsonhas CORS headers for/components.jsonand/trending-data.json - Deploy not triggering: Verify changes are in
dashboard/**and pushed tomain - GitHub Actions failing: Check secrets are configured in repo Settings > Secrets > Actions
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 · 98 lines · 38 tokens per session scan A 05c8dfc88dae
deployer is an agent published in the GitHub repository davila7/claude-code-templates (32,670 stars, last pushed yesterday), licensed MIT. It adds 38 tokens to every session and 727 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
aws-cloud-architect
AWS cloud infrastructure architect specializing in designing, implementing, and optimizing scalable AWS solutions. Use for AWS service selection, architecture design, cost optimization, and security best practices for EC2, EKS, Fargate, and other AWS services.
data-engineer
Build scalable data pipelines, modern data warehouses, and real-time streaming architectures. Implements Apache Spark, dbt, Airflow, and cloud-native data platforms. Use PROACTIVELY for data pipeline design, analytics infrastructure, or modern data stack implementation.
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…
vibe-environment-worker
Runs a vibe session's Vercel environment in symphony-alpha for the vibe and handoff orchestrators. Create mode takes the production flag snapshot in PostHog for the person's real account, pushes the vibe/ branch, starts the environment through the repo's request workflow, follows it to the end, and records the app…
aws-expert
AWS services architecture (Lambda, ECS, S3, RDS, SQS, CloudFront), IaC patterns, and cost optimization specialist.