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/yaleh/meta-cc/claude-mdgit clone --depth 1 https://github.com/yaleh/meta-ccWrote 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/yaleh/meta-cc/claude-md)<a href="https://agentmods.dev/instructions/yaleh/meta-cc/claude-md"><img src="https://agentmods.dev/badge/instructions/yaleh/meta-cc/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.1 | $0.03786 | $0.03786 |
| Opus 5 | $0.01893 | $0.01893 |
| Sonnet 5 | $0.00757 | $0.00757 |
| Haiku 4.5 | $0.00379 | $0.00379 |
Grade A, and why
meta-cc 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 5d 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 — 374 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 when working with code in this repository.
Quick Links
New to meta-cc?
- Start here: README.md - Installation and quick start
- Understand the design: docs/core/principles.md - Core constraints
- Integration guide: docs/guides/integration.md - Choose MCP/Slash
Development Workflow
- Current plan: docs/core/plan.md - Phase roadmap and status
- Build and test: Run
make dev(quick) →make commit(validate) →make push(full check) - Plugin development: docs/guides/plugin-development.md - Complete workflow
MCP Server Usage
- MCP guide: docs/guides/mcp.md - Complete MCP reference (16 tools)
- Quick test: Use MCP tool
get_session_stats
Common Tasks
- Fix test failures:
make dev→ Review errors → Fix →make commit - Query session data: Use MCP tools (see MCP Guide)
- Update plugin: docs/guides/plugin-development.md
- Manage prompts:
/prompt-list(browse) |/prompt-find <keywords>(search) |/prompt-show <id>(view)
FAQ
Q: Tests failed after my changes - what should I do?
A: Run make dev for quick iteration, then make commit to validate. Fix issues iteratively. If tests fail after multiple attempts, HALT development and document blockers.
Q: How much code can I write in one phase? A: Maximum 500 lines of code modifications per phase, 200 lines per stage. See docs/core/principles.md.
Q: Should I use MCP or Slash Commands? A: Quick rule: Natural questions → MCP | Repeated workflows → Slash. See docs/guides/integration.md.
Q: How do I query session data? A: Use consolidated query tools for common questions and the two-stage tools for custom jq:
// Consolidated query tools
query_session_signals({type: "errors", limit: 10})
query_session_signals({type: "tokens", stats_first: true})
query_session_content({role: "user", pattern: "fix.*bug"})
// Custom jq over selected files
execute_stage2_query({
files: ["/path/to/session.jsonl"],
filter: 'select(.type == "assistant")',
transform: '{timestamp, usage: .message.usage}'
})
See MCP Query Tools Reference and Two-Stage Query Guide for complete documentation.
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.
- 5d ago First seen · 374 lines · 3,786 tokens per session scan A 91adf2d8e68e
meta-cc CLAUDE.md is an instructions file published in the GitHub repository yaleh/meta-cc (21 stars, last pushed 14d ago), licensed MIT. It adds 3,786 tokens to every session, about $0.0189 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
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.
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.
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.
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).