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/stuartshields/claude-setup/claude-mdgit clone --depth 1 https://github.com/stuartshields/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/stuartshields/claude-setup/claude-md)<a href="https://agentmods.dev/instructions/stuartshields/claude-setup/claude-md"><img src="https://agentmods.dev/badge/instructions/stuartshields/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 | $0.00807 | $0.00807 |
| Opus 5 | $0.00404 | $0.00404 |
| Sonnet 5 | $0.00161 | $0.00161 |
| Haiku 4.5 | $0.00081 | $0.00081 |
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 3d 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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GLOBAL PROTOCOL (v2026.2)
0. SHORTCUTS & TRIGGERS
- Bootstrap Trigger: If the current directory lacks a
CLAUDE.md, immediately perform DYNAMIC PROJECT INITIALIZATION. - "Trace" or "/trace": Perform a deep-trace audit per the
debuggingskill (~/.claude/skills/debugging/SKILL.md).
1. MANDATORY WORKFLOW
- Verify: After implementing, run the project's build/test/lint command. If it fails, diagnose and fix before moving on. Never mark work as done without verifying it runs.
- On Compaction: Always preserve in the summary: all modified file paths, the current task and acceptance criteria, test commands and results, key decisions and reasoning.
- CLAUDE.md is the Source of Truth: Before making changes, read the project's
CLAUDE.md. If your changes diverge from what it specifies, ask the user: "This differs from the project CLAUDE.md - should I update it first?" Update CLAUDE.md early - when you discover a new convention, make an architecture decision, or establish a pattern, propose the update immediately. Do not wait until the end of the task. Sessions can crash, compact, or be interrupted - anything not written to CLAUDE.md is lost.
2. DYNAMIC PROJECT INITIALIZATION / MIGRATION
- Condition: No local CLAUDE.md:
- Scan configs (
package.json,requirements.txt, etc.). - Identify stack & commands (build/test/lint).
- If Node project: ensure
.nvmrcpins22andpackage.jsonhas"engines": { "node": ">=22" }. Runnvm use 22before any install/dev command. Honour an existing pin and surface divergence — seerules/environment.md"Node Version". - Create local
CLAUDE.mdwith project-specific conventions. Code-quality expectations (DRY, single responsibility, no defensive scaffolding, no commented-out code, named constants) live in~/.claude/rules/code-quality.mdand apply across all projects.
- Scan configs (
- Condition: Local CLAUDE.md exists but is legacy:
- Strip redundant rules (global rules in
~/.claude/rules/are auto-loaded). - Keep only project-specific conventions.
- Standardize indents to Tabs.
- Strip redundant rules (global rules in
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.
- 3d ago First seen · 36 lines · 807 tokens per session scan A cff4ce8c65da
claude-setup CLAUDE.md is an instructions file published in the GitHub repository stuartshields/claude-setup (2 stars, last pushed 3mo ago), licensed MIT. It adds 807 tokens to every session, about $0.0040 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
.agents AGENTS.md
AGENTS.md instructions for Weaverse/.agents, covering agent guidelines for .agents, repository structure, build, lint & test commands, validation commands and validate json configuration.
rules-for-claude CLAUDE.md
Claude Code instructions for chancegraff/rules-for-claude, covering global coding standards, prose style, context efficiency, subagent discipline and file reading.
codeforges-claude-plugin CLAUDE.md
Claude Code instructions for rubenCodeforges/codeforges-claude-plugin, covering claude code plugin development guide, plugin purpose, important rules, when modifying agents and file structure.
SeekMoney-ai CLAUDE.md
Instructions for zykooooooooo/SeekMoney-ai, covering claude.md, project overview, development commands, development and production.
delphi-spec-kit AGENTS.md
Instructions for delphicleancode/delphi-spec-kit, covering delphi ai spec-kit — agents.md, language and stack, naming conventions — pascal guide, general rule and mandatory prefixes.
outlook-mcp CLAUDE.md
Claude Code instructions for ryaker/outlook-mcp, covering claude.md, development commands, architecture overview, core structure and modules.