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 jeromwolf/templateclaw --skill templateclaw-devgit clone --depth 1 https://github.com/jeromwolf/templateclawWrote 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/jeromwolf/templateclaw/templateclaw-dev)<a href="https://agentmods.dev/skills/jeromwolf/templateclaw/templateclaw-dev"><img src="https://agentmods.dev/badge/skills/jeromwolf/templateclaw/templateclaw-dev/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/jeromwolf/templateclaw/templateclaw-dev"><img src="https://agentmods.dev/badge/skills/jeromwolf/templateclaw/templateclaw-dev.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.00037 | $0.00928 |
| Opus 5.5 | $0.00015 | $0.00371 |
| Sonnet 5.5 | $0.00007 | $0.00186 |
| Haiku 4.5 | $0.00004 | $0.00093 |
Grade A, and why
templateclaw-dev 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 2mo 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TemplateClaw — Dev Methodology Guides
Generate actionable development methodology guides and configurations.
When Invoked
- If argument provided (e.g.,
/templateclaw-dev tdd), generate that guide - If no argument, ask: "Which guide? (tdd / cicd / review / git / api)"
Available Guides
TDD Workflow Guide (/templateclaw-dev tdd)
Generate for the detected project language:
Output files:
docs/tdd-guide.md— Step-by-step TDD workflow- Test config file (jest.config.js / pytest.ini / etc.)
- Example test file demonstrating Red→Green→Refactor
Content:
# TDD Workflow
## The Cycle
1. RED: Write a failing test
2. GREEN: Write minimum code to pass
3. REFACTOR: Clean up, maintain tests passing
## Rules
- Never write production code without a failing test
- One assert per test (when possible)
- Test behavior, not implementation
## Test Structure (AAA)
- Arrange: Set up test data
- Act: Execute the behavior
- Assert: Verify the outcome
## Coverage Targets
- Unit: 80%+
- Integration: 60%+
- E2E: Critical paths only
CI/CD Pipeline Setup (/templateclaw-dev cicd)
Detect repository and generate:
GitHub Actions (.github/workflows/ci.yml):
- Lint → Test → Build → Deploy
- Matrix testing (Node 18/20/22 or Python 3.10/3.11/3.12)
- Caching (node_modules / pip / cargo)
- Security scanning (npm audit / safety / cargo audit)
- Deployment (conditional on branch)
Output: Working CI/CD config + docs/cicd-guide.md explaining each stage.
Code Review Checklist (/templateclaw-dev review)
Output: docs/code-review-checklist.md
## Pre-Review (Author)
- [ ] Tests pass locally
- [ ] No lint warnings
- [ ] Self-reviewed diff
- [ ] PR description explains WHY
## Logic & Correctness
- [ ] Edge cases handled
- [ ] Error paths covered
- [ ] No off-by-one errors
- [ ] Concurrency-safe (if applicable)
## Security
- [ ] No hardcoded secrets
- [ ] Input validation at boundaries
- [ ] SQL injection prevented (parameterized queries)
- [ ] XSS prevention (output encoding)
## Performance
- [ ] No N+1 queries
- [ ] Appropriate indexing
- [ ] No unnecessary re-renders (frontend)
## Maintainability
- [ ] Functions under 50 lines
- [ ] Clear naming (no abbreviations)
- [ ] DRY without over-abstraction
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.
- 2mo ago First seen · 134 lines · 37 tokens per session scan A 2a66eac8544c
templateclaw-dev is a skill published in the GitHub repository jeromwolf/templateclaw (3 stars, last pushed 7mo ago), licensed MIT. It adds 37 tokens to every session and 928 once invoked, about $0.0001 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-31.
Other skills, from other repositories
init-pipeline
Infrastructure skill for scaffolding pipeline enforcement into a project. Sets up Claude Code hooks (TDD classification gate, git guardrails, optional quality gate), pre-commit hooks (detects existing tools, defaults to Lefthook + Biome + pnpm if none found). Run when setting up a project for pipeline work, and again…
tdd
Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.
principle-test-behavior-not-implementation
Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.
shift-left-testing
Move quality earlier in the development lifecycle. Covers dev/QA pairing patterns, Three Amigos sessions, TDD facilitation (Red-Green-Refactor), PR review checklists for testability, and Definition of Done with quality gates. Includes shift-left maturity model for team assessment. Use when: "shift left," "TDD,"…
shopify-ab-testing
Run data-driven A/B tests on your Shopify store. Test product pages, pricing, images, copy, checkout flow, and marketing campaigns with proper statistical methodology.
auto-loop
TDD-based autonomous development loop with checkpoint recovery and observability changelog.