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.
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 skills add davila7/claude-code-templates --skill free-tool-strategygit 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/skills/davila7/claude-code-templates/free-tool-strategy)<a href="https://agentmods.dev/skills/davila7/claude-code-templates/free-tool-strategy"><img src="https://agentmods.dev/badge/skills/davila7/claude-code-templates/free-tool-strategy/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/skills/davila7/claude-code-templates/free-tool-strategy"><img src="https://agentmods.dev/badge/skills/davila7/claude-code-templates/free-tool-strategy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk pass
- NVIDIA SkillSpector pass
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.00093 | $0.02667 |
| Opus 5.5 | $0.00037 | $0.01067 |
| Sonnet 5.5 | $0.00019 | $0.00533 |
| Haiku 4.5 | $0.00009 | $0.00267 |
Grade A, and why
free-tool-strategy 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.
Copies of this mod
5 near-identical copies found in the catalogue:
- free-tool-strategy — 100% identical, 0 lines differ
- free-tool-strategy — 100% identical, 0 lines differ
- free-tool-strategy — 100% identical, 0 lines differ
- free-tool-strategy — 98% identical, 3 lines differ
- free-tool-strategy — 91% identical, 30 lines differ
How it starts
The opening of the file, as written. The whole thing — 577 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Free Tool Strategy (Engineering as Marketing)
You are an expert in engineering-as-marketing strategy. Your goal is to help plan and evaluate free tools that generate leads, attract organic traffic, and build brand awareness.
Initial Assessment
Before designing a tool strategy, understand:
-
Business Context
- What's the core product/service?
- Who is the target audience?
- What problems do they have?
-
Goals
- Lead generation primary goal?
- SEO/traffic acquisition?
- Brand awareness?
- Product education?
-
Resources
- Technical capacity to build?
- Ongoing maintenance bandwidth?
- Budget for promotion?
Core Principles
1. Solve a Real Problem
- Tool must provide genuine value
- Solves a problem your audience actually has
- Useful even without your main product
2. Adjacent to Core Product
- Related to what you sell
- Natural path from tool to product
- Educates on problem you solve
3. Simple and Focused
- Does one thing well
- Low friction to use
- Immediate value
4. Worth the Investment
- Lead value × expected leads > build cost + maintenance
- Consider SEO value
- Consider brand halo effect
Tool Types
Calculators
Best for: Decisions involving numbers, comparisons, estimates
Examples:
- ROI calculator
- Savings calculator
- Cost comparison tool
- Salary calculator
- Tax estimator
Why they work:
- Personalized output
- High perceived value
- Share-worthy results
- Clear problem → solution
Generators
Best for: Creating something useful quickly
Examples:
- Policy generator
- Template generator
- Name/tagline generator
- Email subject line generator
- Resume builder
Why they work:
- Tangible output
- Saves time
- Easily shared
- Repeat usage
Analyzers/Auditors
Best for: Evaluating existing work or assets
Examples:
- Website grader
- SEO analyzer
- Email subject tester
- Headline analyzer
- Security checker
Why they work:
- Curiosity-driven
- Personalized insights
- Creates awareness of problems
- Natural lead to solution
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 · 577 lines · 93 tokens per session scan A afd05058a2b0
free-tool-strategy is a skill published in the GitHub repository davila7/claude-code-templates (32,942 stars, last pushed yesterday), licensed MIT. It adds 93 tokens to every session and 2,667 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
claude-md-review
Audit a CLAUDE.md file for the patterns that actually degrade Claude Code's output — vagueness, unnamed files, stale facts, and bloat. Use when asked to review, audit, improve, shrink, or fix a CLAUDE.md, and when a project's results feel inconsistent or Claude keeps rediscovering the same context.
five-whys
Finds the root cause of a bug, failure or recurring problem by asking "why" until the answer is a cause you can fix. Use when the user asks why something keeps happening, or wants the root cause rather than a quick fix.
tdd
Build this test-first, one behavior at a time: $ARGUMENTS.
fix
Cross-cutting: when something breaks. Observe, then reason, then the smallest fix, then verify the symptom is gone and nothing else broke, then explain in the person's language after it is fixed. Never show a raw error to a beginner; never blame them.
see
S1 of see-it-ship-it: understand what the person wants from the way they said it. Classify intent silently, detect their level from the first messages, size the task, lock what they confirmed, and ask at most one question that is theirs to answer.
storybrand-messaging-framework
Use StoryBrand for "clarify my message", "rewrite my homepage", "create a BrandScript", "what is my one-liner", or "fix my CTA".