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/nwiizo/ccat/claude-mdgit clone --depth 1 https://github.com/nwiizo/ccatWrote 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/nwiizo/ccat/claude-md)<a href="https://agentmods.dev/instructions/nwiizo/ccat/claude-md"><img src="https://agentmods.dev/badge/instructions/nwiizo/ccat/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.00823 | $0.00823 |
| Opus 5 | $0.00411 | $0.00411 |
| Sonnet 5 | $0.00165 | $0.00165 |
| Haiku 4.5 | $0.00082 | $0.00082 |
Grade A, and why
ccat 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 — 122 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.
Project Overview
This is ccat, a command-line tool for analyzing and managing Claude Code memory files (CLAUDE.md). It's built in Rust and provides comprehensive analysis, diagnostics, and export capabilities for CLAUDE.md files across different scopes (user, project, subdirectory).
Installation
From crates.io (Recommended)
cargo install ccat
From source
git clone https://github.com/nwiizo/ccat.git
cd ccat
cargo install --path .
Development Commands
Essential Commands
# Build and run quality checks (recommended before commits)
just check
# Auto-fix formatting and clippy issues
just fix
# Build release binary
just build
# Run tests
just test
# Install locally
just install
Development Workflow
# Format code
cargo fmt
# Run lints
cargo clippy --all-targets --all-features -- -D warnings
# Run specific tests
cargo test [test_name]
# Run benchmarks
cargo bench
# Generate and open documentation
cargo doc --open
Architecture Overview
The codebase is organized into five main modules:
Core Module (src/core/)
- Scanner: Discovers CLAUDE.md files in filesystem hierarchy
- Parser: Parses memory files and extracts imports/metadata
- Resolver: Resolves import chains and validates references
- Cache: LRU caching system for parsed files
CLI Module (src/cli/)
- Commands: Eight main commands (show, diagnose, search, diff, watch, export, validate, init)
- Args: Command-line argument definitions and parsing
- Entry point that routes to appropriate command handlers
Analyzer Module (src/analyzer/)
- Diagnostics: Detects issues like circular imports, missing files, large contexts
- Security: Scans for exposed secrets, API keys, passwords
- Validator: Validates memory file structure and content
- Profiler: Performance metrics and analysis
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 · 122 lines · 823 tokens per session scan A bde113d9eb46
ccat CLAUDE.md is an instructions file published in the GitHub repository nwiizo/ccat (33 stars, last pushed 1mo ago), licensed MIT. It adds 823 tokens to every session, about $0.0041 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.