Borrowing it
Nothing to install: this file belongs to etrebels/claude-code-growth-os. 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/etrebels/claude-code-growth-os/main/CLAUDE.mdgit clone --depth 1 https://github.com/etrebels/claude-code-growth-osWrote 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/etrebels/claude-code-growth-os/claude-md)<a href="https://agentmods.dev/instructions/etrebels/claude-code-growth-os/claude-md"><img src="https://agentmods.dev/badge/instructions/etrebels/claude-code-growth-os/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/etrebels/claude-code-growth-os/claude-md"><img src="https://agentmods.dev/badge/instructions/etrebels/claude-code-growth-os/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.00586 | $0.00586 |
| Opus 5.5 | $0.00234 | $0.00234 |
| Sonnet 5.5 | $0.00117 | $0.00117 |
| Haiku 4.5 | $0.00059 | $0.00059 |
Grade B, and why
claude-code-growth-os 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 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.
Reads MCP configurationmediumAgent snooping
mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.
Add MCP servers (calendar, notes, issue tracker, CRM) by copying `.mcp.json.example` → `.mcp.json` (gitignored), then let your commands and skills reach them. Keep machine-local config and secrets in `.claude/settings.lo How it starts
The opening of the file, as written. The whole thing — 22 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@AGENTS.md
Claude Code Growth OS — Claude Code notes
The working conventions, repository layout, rituals, hooks, rules and scheduling
are in AGENTS.md, imported above, so every coding agent reads the
same file. What follows is the part that only applies to Claude Code.
Open-PR hygiene
This repo has accumulated open, unmerged PRs from prior sessions (7 open as of 2026-07-05; #38 has since merged, but the count has since drifted back up to 6 as of 2026-08-09, several dating to early July). Before opening a new PR: check repo:etrebels/claude-code-growth-os is:pr is:open for existing work on the same topic and continue or merge it rather than adding a near-duplicate. If a recurring skill's own prior PR is still open, that's a signal worth surfacing in its output, not a fresh PR to pile on top.
The rule keeps getting proven on insights-loop itself. #38 sat unmerged for four weeks before merging; its successor, #53 (opened 2026-07-19, "codify /babysit-prs, fix hygiene drift" — itself a fix for this exact problem), sat as a draft for three weeks and has since drifted into a real merge conflict with main (mergeable_state: dirty) as unrelated content landed on top of it. A routine that opens a fresh dated branch every week without checking back on last week's branch is how PRs pile up, not just a bystander reporting it — the fix is to extend or close out the prior branch before starting a new one, not just to log the number.
Session-analysis routines (e.g. insights-loop)
A remote/cloud session starts from a fresh clone every run — nothing under ~/.claude/projects/ (session transcripts) persists across sessions. "Analyze the last N days of Claude Code session transcripts" therefore has no literal data to read beyond the current run's own in-progress transcript. Any routine making that claim should fall back to evidence that does persist — git log --since, open/merged PR history and their review comments, and CI check runs — and say plainly that it's using that fallback rather than implying it read transcripts that don't exist in this environment.
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 Changed · -35 lines · -1,536 tokens per session c0f4cf62b55d
- 1mo ago Changed · +5 lines · +477 tokens per session a78005df8901
- 1mo ago First seen · 52 lines · 1,645 tokens per session scan B eb57de1f9405
claude-code-growth-os CLAUDE.md is an instructions file published in the GitHub repository etrebels/claude-code-growth-os (21 stars, last pushed 7d ago), licensed MIT. It adds 586 tokens to every session, about $0.0023 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads mcp configuration). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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.