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/cocaxcode/ai-context-inspector/claude-mdgit clone --depth 1 https://github.com/cocaxcode/ai-context-inspectorWrote 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/cocaxcode/ai-context-inspector/claude-md)<a href="https://agentmods.dev/instructions/cocaxcode/ai-context-inspector/claude-md"><img src="https://agentmods.dev/badge/instructions/cocaxcode/ai-context-inspector/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.01328 | $0.01328 |
| Opus 5 | $0.00664 | $0.00664 |
| Sonnet 5 | $0.00266 | $0.00266 |
| Haiku 4.5 | $0.00133 | $0.00133 |
Grade A, and why
ai-context-inspector 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 3d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — @cocaxcode/ai-context-inspector
Project Overview
CLI + MCP server that scans projects to discover their complete AI ecosystem. Export/import configs between 7 AI tools. 5 MCP tools, 104 tests.
Stack
- TypeScript 5.x (strict mode, ESM)
- @modelcontextprotocol/sdk 1.27.x (client + server)
- Zod 3.25+ for schema validation
- Vitest for testing
- tsup for building (ESM output with shebang)
Architecture
src/
├── index.ts # Entry: CLI vs MCP mode routing
├── cli.ts # CLI arg parsing + orchestration (scan, export, import subcommands)
├── server.ts # createServer() MCP factory
├── scanner/
│ ├── types.ts # All TypeScript interfaces
│ ├── catalog.ts # AI_FILE_CATALOG (40+ entries, 13 tools)
│ ├── index.ts # runAllScanners() orchestrator
│ ├── context-files.ts # Scan context files (.md, rules, configs)
│ ├── mcp-configs.ts # Parse .mcp.json, ~/.claude.json, etc.
│ ├── mcp-introspect.ts # Connect to MCP servers, list tools/resources/prompts
│ ├── skills.ts # Scan skill directories + registry
│ └── memories.ts # Detect engram, openspec, .atl
├── ecosystem/ # Export/import module
│ ├── types.ts # EcosystemBundle, ImportTarget, options interfaces
│ ├── index.ts # Re-exports all public API
│ ├── export.ts # exportEcosystem() — scan → bundle → .aci/bundle.json
│ ├── import.ts # loadBundle(), planImport(), executeImport()
│ ├── target-map.ts # TARGET_CONFIGS for 7 AI tools (paths, formats)
│ ├── detect-target.ts # Auto-detect which AI tool is used in a project
│ ├── secrets.ts # Env var detection, sensitive pattern matching
│ └── prompts.ts # Interactive CLI prompts (categories, secrets, confirm)
├── report/
│ ├── generator.ts # generateHtml(ScanResult) → string
│ ├── sections.ts # HTML section renderers
│ ├── styles.ts # CSS (dark/light mode)
│ └── scripts.ts # JS (collapse, search, preview)
├── tools/
│ ├── scan.ts # MCP tool: scan project
│ ├── introspect.ts # MCP tool: introspect specific MCP
│ ├── report.ts # MCP tool: generate HTML report
│ ├── export.ts # MCP tool: export_ecosystem
│ └── import.ts # MCP tool: import_ecosystem
└── __tests__/
├── fixtures/ # Test projects (full, empty, mcp-only, export-project)
├── helpers.ts # fixture() path helper
└── *.test.ts # 10 test files, 104 tests
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.
- 3d ago First seen · 107 lines · 1,328 tokens per session scan A 9d7d06655fbc
ai-context-inspector CLAUDE.md is an instructions file published in the GitHub repository cocaxcode/ai-context-inspector (1 stars, last pushed 5mo ago), licensed MIT. It adds 1,328 tokens to every session, about $0.0066 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-31.
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.