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/madappgang/claude-code/claude-mdgit clone --depth 1 https://github.com/MadAppGang/claude-codeWrote 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/madappgang/claude-code/claude-md)<a href="https://agentmods.dev/instructions/madappgang/claude-code/claude-md"><img src="https://agentmods.dev/badge/instructions/madappgang/claude-code/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.02947 | $0.02947 |
| Opus 5 | $0.01473 | $0.01473 |
| Sonnet 5 | $0.00589 | $0.00589 |
| Haiku 4.5 | $0.00295 | $0.00295 |
Grade A, and why
claude-code 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 4d 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 — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Context for Claude Code
CRITICAL RULES
NEVER use pkill or broad process-killing commands (like pkill -f "claudeup" or pkill -f "claude"). This kills all Claude CLI sessions running on the machine. Instead, ask the user to restart applications manually or close specific windows.
Project Overview
Repository: MAG Claude Plugins Purpose: Professional plugin marketplace for Claude Code Owner: Jack Rudenko ([email protected]) @ MadAppGang License: MIT
Plugins
| Plugin | Version | Purpose |
|---|---|---|
| Frontend | v3.15.1 | React/TypeScript dev with 11 agents, multi-model review |
| Code Analysis | v3.2.2 | Codebase investigation with claudemem, enrichment mode (non-blocking) |
| Bun Backend | v1.6.1 | TypeScript backend with Bun, Apidog integration |
| Orchestration | v0.8.2 | Multi-agent coordination patterns (6 skills) |
| Agent Development | v1.5.2 | Create Claude Code agents and plugins |
| SEO | v1.6.2 | SEO analysis and optimization with AUTO GATEs |
| Video Editing | v1.0.1 | FFmpeg, Whisper, Final Cut Pro integration |
| Nanobanana | v2.2.3 | AI image generation with Gemini 3 Pro Image |
| Dev | v1.31.2 | Universal dev assistant with real validation loops, 46 skills |
Claudish CLI: npm install -g claudish - Run Claude with OpenRouter models (separate repo)
Key Architecture Decisions
1. Team-First Configuration
Shareable (committed to git):
- Project IDs, URLs, configuration
.claude/settings.jsonwith project config- No secrets
Private (environment variables):
- API tokens, credentials
- Each developer's
.envfile - Never committed
2. Smart Validation
Configuration commands check existing setup before asking questions, validate credentials before saving.
3. Project-Specific Installation
Plugins can be installed:
- Globally (all projects)
- Per-project (
.claude/settings.json) - Teams use project-specific for consistency
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.
- 4d ago First seen · 275 lines · 2,947 tokens per session scan A 893933d49802
claude-code CLAUDE.md is an instructions file published in the GitHub repository MadAppGang/claude-code (279 stars, last pushed 5mo ago), licensed MIT. It adds 2,947 tokens to every session, about $0.0147 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
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.