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/cbmono/ai-setup/claude-mdgit clone --depth 1 https://github.com/cbmono/ai-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/cbmono/ai-setup/claude-md)<a href="https://agentmods.dev/instructions/cbmono/ai-setup/claude-md"><img src="https://agentmods.dev/badge/instructions/cbmono/ai-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.04493 | $0.04493 |
| Opus 5 | $0.02246 | $0.02246 |
| Sonnet 5 | $0.00899 | $0.00899 |
| Haiku 4.5 | $0.00449 | $0.00449 |
Grade A, and why
ai-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 — 115 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.
@.claude/claude-defaults.md @.claude/MEMORY.md
What this repo is
Public, opinionated Claude Code defaults for Node.js / TypeScript projects. It ships subagents, user-invocable slash commands, a permissions baseline, and a CLAUDE.md template that users drop into consumer projects. No application code and no build step. It does have a test suite: POSIX shell harnesses under tests/ covering the installer, the rule globs, the skills allowlist, the DeepSeek launcher's secret handling, the shipped commands' hardening (config-hardening) and who owns each ~/.claude path (claude-config-ownership) — run them all before pushing. So work here is markdown and JSON under .claude/, the top-level README.md, and shell under tests/, .claude/hooks/, .claude/scripts/ and install.sh. This sentence used to read "no test suite … markdown and JSON", which was true when it was written and has been false for a while; a reviewer reading it as policy asked for shell changes to be removed. If you add a new kind of file here, fix this line in the same commit.
This repo owns ~/.claude
Two installers used to claim ${CLAUDE_CONFIG_DIR:-~/.claude}: this one, and the config/
layer of cbmono/ai-bridge, which was a fork of this .claude/ tree. 24 of 26 entries
were shipped by both and 14 had diverged, so ownership was decided by whichever installer
ran last. The cost was not cosmetic: fixes made in the private fork — including two
secret-exposure paths — sat there for weeks while this public repo shipped the defects.
Resolved by making this repo the owner. ai-bridge keeps only config/required/ (the three
agents it probes for by absolute path: code-architect, deep-bug-scan, plan-architect)
and installs nothing else. Consequences when working here:
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 · 115 lines · 4,493 tokens per session scan A 78e86361a2db
ai-setup CLAUDE.md is an instructions file published in the GitHub repository cbmono/ai-setup (2 stars, last pushed 9d ago), licensed MIT. It adds 4,493 tokens to every session, about $0.0225 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
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).
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.