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/darkroomengineering/cc-settings/claude-mdgit clone --depth 1 https://github.com/darkroomengineering/cc-settingsWhat 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.00699 | $0.00699 |
| Opus 5 | $0.00349 | $0.00349 |
| Sonnet 5 | $0.00140 | $0.00140 |
| Haiku 4.5 | $0.00070 | $0.00070 |
Grade B, and why
cc-settings CLAUDE.md scanned grade B with 1 finding 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 2d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
fragments that are *composed* into `~/.claude/settings.json` at install time How it starts
The opening of the file, as written. The whole thing — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cc-settings
Darkroom Engineering Claude Code configuration repository.
Important
This repo contains two config files installed globally:
AGENTS.md→~/.claude/AGENTS.md(portable coding standards, reference copy)CLAUDE-FULL.md→~/.claude/CLAUDE.md(Claude-Code-specific config)
The AGENTS.md file is the source of truth for coding standards and guardrails.
It works across all AI coding tools (Codex, Cursor, Copilot, Windsurf, etc.).
CLAUDE-FULL.md contains only Claude-Code-specific settings (edit strategy,
delegation guidance, model config, profiles, hooks). It points to AGENTS.md
for standards.
About This Repo
TypeScript on Bun (migrated from bash in April 2026; see git log for history). Runtime: bun >=1.2.21. Skill count and the soft cap of 40 are enforced by bun run lint:skills — provenance and the cap rule live in CLAUDE-FULL.md ("Skill library soft cap"), not here.
Deps: zod (only — yaml and @inquirer/confirm were dropped for Bun.YAML
and node:readline). Dev: @biomejs/biome, typescript, @types/bun.
Two directories aren't what their names suggest: config/ holds settings
fragments that are composed into ~/.claude/settings.json at install time
(edit those, never the installed file), and schemas/*.schema.json is
generated from the zod sources in src/schemas/ — don't hand-edit it.
Development
- Install:
bash setup.sh(macOS/Linux) or.\setup.ps1(Windows) - Light install:
bash setup.sh --light(raw Claude Code + statusline +share-learningskill only; permanent beginner tier — re-run without--lightto upgrade) - Rollback:
bun src/setup.ts --rollback(restores newest backup) - Fresh install:
bash setup.sh --fresh(reinstall as if from scratch — settings.json, prior-install state, and local approvals reset; login/history/memory untouched; recover via rollback) - Dry-run:
bun src/setup.ts --dry-run - Tests:
bun test - Typecheck:
bun run typecheck - Lint:
bun run lint/bun run lint:fix - Deliberate-shortcut markers:
bun run lint:shortcuts(add-- --ledgerfor the/audit debtview). Convention lives in AGENTS.md → Laziness Ladder. - Schemas (regenerate JSON Schema from zod sources):
bun run schemas:emit - Preview composed settings.json:
bun run compose - Dry-run a Bash command against the permission rules:
bun run permissions:check "<cmd>"(--installedto check against~/.claude/settings.jsoninstead ofconfig/) - Upstream drift scan:
bun run upstream:scan - Commits: conventional —
feat:,fix:,refactor:,docs:,chore:,test:.
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.
- 2d ago First seen · 45 lines · 699 tokens per session scan B ba5c4fe5a7a8
cc-settings CLAUDE.md is an instructions file published in the GitHub repository darkroomengineering/cc-settings (42 stars, last pushed 4d ago), licensed MIT. It adds 699 tokens to every session, about $0.0035 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
agents-config CLAUDE.md
Claude Code instructions for artivilla/agents-config, covering agent config, commands, testing, key files and verification.
ken CLAUDE.md
Instructions for townsendmerino/ken, covering claude.md, what this is, repository ownership (read this first), commands and embedding parity & golden fixtures (now in aikit).
gangsta GEMINI.md
Instructions for kucherenko/gangsta, a project described as: AI agentic skills framework for spec-driven development, built on the organizational model of mafia.
AI-System-Design-Consultant CLAUDE.md
Instructions for deepanshu2711/AI-System-Design-Consultant, covering claude.md, what this is, running it, load-bearing typos — do not "fix" these paths and agent node pattern.
dotfiles CLAUDE.md
Claude Code instructions for M0rtalPhe0nix/dotfiles, covering coding agent instructions, repository purpose, safety rules, chezmoi conventions and operational invariants.
cortex AGENTS.md
AGENTS.md instructions for tools-for-agents/cortex, covering agents.md — cortex, setup, the rules this repo is built on, tests and ci.