About Claude Code Templates
Claude Code Templates, at aitmpl.com, is an open-source registry and command-line tool for discovering, inspecting and installing components for Claude Code: subagents, slash commands, skills, hooks, MCP server configurations, settings, loops and mods. It is maintained by Daniel Avila together with community contributors, and every component lives in the public GitHub repository.
Why it exists
Claude Code is configured through small, composable files, but good ones are scattered across personal repositories, gists and blog posts. There was no reliable way to find them, judge whether they are safe to run, or install them without copying files by hand. Hooks and MCP servers matter most here, because they run code with your local permissions. Component authors had the opposite problem: no neutral place to show their work to the people who would use it.
What it does
- Web catalog. Every component has a page with its source, description, install command and a preview of the files it writes.
- CLI.
npx claude-code-templates@latestinstalls any component, or several at once, into the right project or user location and merges existing configuration instead of overwriting it. - Plain files. Components are not a black box. You can read, fork and edit them after installing, and each one links back to its source so changes can go upstream.
Security review
Every pull request that adds or changes a component goes through automated code review, a component validation pipeline and, for skills, the SkillSpector static security scanner. Components that execute code, such as hooks and MCP servers, get extra scrutiny of what they run and what they access. Still, read a component before you install it, especially one that runs commands.
Sponsored placements
Component authors and companies can pay for a sponsored placement: one component shown in a slot at the top of search results and as the first card of the component grid. That slot always carries a "Sponsored" label and the component passes the same review as any other. Payment never changes the order of the other results, the categories or the install recommendations. The revenue pays for hosting, security tooling and maintainer time.
Neutrality
The project is not a company and is not raising money. Components are judged on quality and safety, not on who built them or who paid. The code is MIT licensed.
Contact
Bugs, component requests and contributions go to GitHub issues. Security reports follow the security policy. For anything else, email [email protected]. Documentation is at docs.aitmpl.com.