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 instructions/justdvp/claude-code-templates/claude-mdgit clone --depth 1 https://github.com/Justdvp/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/instructions/justdvp/claude-code-templates/claude-md)<a href="https://agentmods.dev/instructions/justdvp/claude-code-templates/claude-md"><img src="https://agentmods.dev/badge/instructions/justdvp/claude-code-templates/claude-md.svg" alt="Measured on agentmods" 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 | $0.04007 | $0.04007 |
| Opus 5 | $0.02004 | $0.02004 |
| Sonnet 5 | $0.00801 | $0.00801 |
| Haiku 4.5 | $0.00401 | $0.00401 |
Grade A, and why
claude-code-templates CLAUDE.md 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 4d 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 — 482 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
This is a Node.js CLI tool for setting up Claude Code configurations and providing real-time analytics. The project uses modern JavaScript/Node.js development practices and includes a comprehensive analytics dashboard with modular architecture.
Development Commands
Package Management
npm install- Install all dependenciesnpm install --save <package>- Install a production dependencynpm install --save-dev <package>- Install a development dependencynpm update- Update all dependenciesnpm audit- Check for security vulnerabilitiesnpm audit fix- Fix security vulnerabilities
Application Commands
npm start- Run the CLI toolnpm run analytics:start- Start the analytics dashboard servernpm run analytics:test- Run analytics-specific testsnode src/analytics.js- Direct analytics server startup
Testing Commands
npm test- Run all tests with Jestnpm run test:watch- Run tests in watch modenpm run test:coverage- Run tests with coverage reportnpm run test:unit- Run unit tests onlynpm run test:integration- Run integration tests onlynpm run test:e2e- Run end-to-end testsnpm run test:analytics- Run analytics module testsnpm run test:all- Run comprehensive test suite
Code Quality Commands
npm run lint- Run ESLint (if configured)npm run format- Format code (if configured)node --check src/analytics.js- Check syntax
Development Tools
npm run dev:link- Link package for local developmentnpm run dev:unlink- Unlink packagenpm version patch|minor|major- Bump versionnpm publish- Publish to npm registry
Analytics Dashboard
Quick Start
# Start the analytics dashboard
npm run analytics:start
# Open browser to http://localhost:3333
# The dashboard provides real-time monitoring of Claude Code sessions
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.
- 4d ago First seen · 482 lines · 4,007 tokens per session scan A e3ada61634d2
claude-code-templates CLAUDE.md is an instructions file published in the GitHub repository Justdvp/claude-code-templates (7 stars, last pushed yesterday), licensed MIT. It adds 4,007 tokens to every session, about $0.0200 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-31.
Other instructions, from other repositories
superpipelines AGENTS.md
AGENTS.md instructions for gustavo-meilus/superpipelines, covering superpipelines agent onboarding, project purpose, stack and runtime, build, test, run and architecture map.
superpipelines GEMINI.md
Gemini CLI instructions for gustavo-meilus/superpipelines, covering superpipelines — antigravity cli 2.0 context, what this plugin does, commands, antigravity-specific paths and migration from gemini cli.
Myco AGENTS.md
Instructions for BreetyGreen/Myco, covering agents.md — orientation for ai agents & contributors, what this project is, architecture (two layers), single source of truth: engine/agents.json and key files.
agentic-delivery-playbook AGENTS.md
Instructions for arcayne/agentic-delivery-playbook: Use adapters/codex/AGENTS.md as the repository operating instructions.
superpipelines CLAUDE.md
Claude Code instructions for gustavo-meilus/superpipelines, a project described as: Loop Engineering for AI coding agents, with real review boundaries. Your AI reviewer cannot edit code. Structurally.
agent-rules child-process.instructions.md
Instructions for lirantal/agent-rules, covering system processes secure coding guidelines, your mission and spawning system processes.