Borrowing it
Nothing to install: this file belongs to shahtuyakov/claude-setup. 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/shahtuyakov/claude-setup/main/CLAUDE.mdgit clone --depth 1 https://github.com/shahtuyakov/claude-setupWrote 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/shahtuyakov/claude-setup/claude-md)<a href="https://agentmods.dev/instructions/shahtuyakov/claude-setup/claude-md"><img src="https://agentmods.dev/badge/instructions/shahtuyakov/claude-setup/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.1 | $0.00738 | $0.00738 |
| Opus 5 | $0.00369 | $0.00369 |
| Sonnet 5 | $0.00148 | $0.00148 |
| Haiku 4.5 | $0.00074 | $0.00074 |
Grade A, and why
claude-setup 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 7d 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 — 75 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.
Repository Overview
This repository contains Claude Code skills, a knowledge base of Anthropic engineering articles, and placeholder directories for agents and hooks.
Structure
claude-setup/
├── agents/
│ ├── 01-effective-harnesses-for-long-running-agents.md
│ ├── 02-advanced-tool-use.md
│ ├── 03-code-execution-with-mcp.md
│ ├── 04-agent-skills.md
│ ├── 05-context-engineering.md
│ ├── 06-multi-agent-research-system.md
│ └── 07-claude-code-best-practices.md
└── skills/ # Claude Code skills
├── api-design-reviewer/ # API review for REST/GraphQL/gRPC
├── brand-guidelines/ # Anthropic brand colors and typography
├── canvas-design/ # Visual art in .png/.pdf with design philosophy
├── frontend-design/ # Production-grade frontend interfaces
└── skill-creator/ # Meta-skill for creating new skills
Knowledge Base
The knowledgebase/ folder contains curated articles from Anthropic's engineering blog. Key concepts:
- Progressive Disclosure: Load information in layers as needed (metadata → SKILL.md → bundled resources)
- Token Efficiency: Code APIs reduce tokens by 98.7%, tool search by 85%, programmatic calling by 37%
- Orchestrator-Worker Pattern: Lead agent delegates to specialized subagents for 90%+ performance gains
- Just-in-Time Loading: Maintain identifiers, load content dynamically instead of pre-loading
- Thinking Modes: Use "think", "think hard", "think harder", "ultrathink" for complex problems
Skill Architecture
Each skill follows this pattern:
skill-name/
├── SKILL.md # Required: YAML frontmatter (name, description) + instructions
├── scripts/ # Optional: Executable Python/Bash scripts
├── references/ # Optional: Documentation loaded into context as needed
└── assets/ # Optional: Templates, fonts, images used in output
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.
- 7d ago First seen · 75 lines · 738 tokens per session scan A ef92cc04b0d7
claude-setup CLAUDE.md is an instructions file published in the GitHub repository shahtuyakov/claude-setup (13 stars, last pushed 8mo ago), licensed MIT. It adds 738 tokens to every session, about $0.0037 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-30.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.