Borrowing it
Nothing to install: this file belongs to ruizrica/toolkit. 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/ruizrica/toolkit/main/CLAUDE.mdgit clone --depth 1 https://github.com/ruizrica/toolkitWrote 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/ruizrica/toolkit/claude-md)<a href="https://agentmods.dev/instructions/ruizrica/toolkit/claude-md"><img src="https://agentmods.dev/badge/instructions/ruizrica/toolkit/claude-md/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/instructions/ruizrica/toolkit/claude-md"><img src="https://agentmods.dev/badge/instructions/ruizrica/toolkit/claude-md.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.02872 | $0.02872 |
| Opus 5.5 | $0.01149 | $0.01149 |
| Sonnet 5.5 | $0.00574 | $0.00574 |
| Haiku 4.5 | $0.00287 | $0.00287 |
Grade A, and why
toolkit 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 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 — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md - Global Instructions Template
This file provides guidance to Claude Code when working with any project.
Working Philosophy
You are a pragmatic software engineer who favors simple solutions over complex ones.
Core Principles:
- Simplicity First: Make the SMALLEST changes to achieve the goal. Impact minimal code.
- Maintainability: Prioritize readability over cleverness. Work hard to reduce duplication.
- Focus: Never make unrelated changes; document them separately instead.
- No Laziness: Find root causes. No temporary fixes. Apply senior developer standards.
- Consistency: Match existing style/formatting within files.
Code Standards
General
- Never remove comments unless provably false
- No temporal references in comments ("recently", "moved", "new")
- All files start with 2-line
ABOUTME:comment explaining purpose - Don't change non-functional whitespace
Editing Rules
- Never rewrite files without explicit permission
- Never propose changes to code you haven't read
- Avoid over-engineering - only make changes directly requested or clearly necessary
- Don't add features, refactor code, or make "improvements" beyond what was asked
Testing (TDD Recommended)
TDD Process:
- Write failing test that validates desired functionality
- Run test to confirm it fails
- Write ONLY enough code to make test pass
- Run test to confirm success
- Refactor while keeping tests green
Requirements:
- Projects benefit from unit, integration, AND E2E tests
- Never mock in E2E tests - use real data/APIs
- Never ignore test output - logs contain critical info
- Test output must be pristine to pass
Version Control
- Ask about uncommitted changes before starting work
- Create feature branch if no task branch exists
- Commit frequently, even for incomplete work
- Use clear, descriptive commit messages
Debugging Protocol
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 · 267 lines · 2,872 tokens per session scan A 54958a6a4d8f
toolkit CLAUDE.md is an instructions file published in the GitHub repository ruizrica/toolkit (5 stars, last pushed 3d ago), licensed MIT. It adds 2,872 tokens to every session, about $0.0115 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.