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/fabio-dee/ccaudit/claude-mdgit clone --depth 1 https://github.com/fabio-dee/ccauditWrote 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/fabio-dee/ccaudit/claude-md)<a href="https://agentmods.dev/instructions/fabio-dee/ccaudit/claude-md"><img src="https://agentmods.dev/badge/instructions/fabio-dee/ccaudit/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.01892 | $0.01892 |
| Opus 5 | $0.00946 | $0.00946 |
| Sonnet 5 | $0.00378 | $0.00378 |
| Haiku 4.5 | $0.00189 | $0.00189 |
Grade A, and why
ccaudit 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Project memory for AI coding assistants working in this repo. For end-user docs see README.md; release notes in CHANGELOG.md; JSON envelope reference in docs/JSON-SCHEMA.md.
Project
ccaudit is a CLI that audits Claude Code's ghost inventory: agents, skills, MCP servers, commands, hooks, and memory files defined once but rarely invoked. It quantifies the per-session token cost and ships one reversible command to archive ghosts. Companion tool to ccusage.
Tech stack
TypeScript / Node ≥20 / pnpm 10 monorepo. CLI built on gunshi. JSON validation via valibot.safeParse. Globbing via tinyglobby. Tables via cli-table3. Bundled via tsdown (Rolldown). Tested via vitest 4.1. Formatted via oxfmt. Linted via eslint 9 flat config. Zero runtime dependencies: everything is devDependencies and bundled into dist/.
Monorepo layout
apps/ccaudit/ CLI entry, subcommand wrappers, integration tests, dist/ bundle
packages/internal/ Domain code: scanner, remediation, framework, token, history, report
packages/terminal/ Terminal renderers (tables, panels, color)
docs/ User-facing reference docs
Commands
pnpm verify # full gate: typecheck + lint + build + test + format:check
pnpm test # vitest only (TZ=UTC enforced, no watch in CI)
pnpm build # tsdown bundle into apps/ccaudit/dist/
pnpm format # oxfmt --write .
CI is tag-triggered only. Pre-push hook runs format + lint (not tests). Run pnpm verify locally before opening a PR.
Conventions
- In-source tests belong in
if (import.meta.vitest) { ... }blocks at the bottom of source files. Integration tests live underapps/ccaudit/src/__tests__/. The bundler strips in-source tests viadefine: { 'import.meta.vitest': 'undefined' }. - Result types: prefer
@praha/byethrowResultover throwing across module boundaries. - Paths: use forward slashes in glob patterns (tinyglobby normalizes).
os.homedir()for home expansion. Never hard-code/Users/...or/home/.... - Time: ISO 8601 UTC strings (
new Date().toISOString()). Tests run withTZ=UTC. - Errors at boundaries: at the outermost layer (CLI command, history writer), catch and degrade gracefully. Inside the domain, propagate via
Result. - Frontmatter writes on memory files: always go through
writeFilePreservingMtimefrompackages/internal/src/remediation/fs-utils.ts. A barefs.writeFiledestroys the staleness signal.
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 · 92 lines · 1,892 tokens per session scan A 03d87843bc0f
ccaudit CLAUDE.md is an instructions file published in the GitHub repository fabio-dee/ccaudit (47 stars, last pushed 4mo ago), licensed MIT. It adds 1,892 tokens to every session, about $0.0095 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.