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/abhisavakar/codeimpact/claude-mdgit clone --depth 1 https://github.com/abhisavakar/codeimpactWhat 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.02782 | $0.02782 |
| Opus 5 | $0.01391 | $0.01391 |
| Sonnet 5 | $0.00556 | $0.00556 |
| Haiku 4.5 | $0.00278 | $0.00278 |
Grade A, and why
codeimpact 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 2d 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 — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Instructions
CLI Commands
codeimpact deadcode # Find unused exports and dead code
codeimpact test-impact --changed src/file.ts # Tests to run for changed files
codeimpact impact src/core/engine.ts # Blast radius analysis
codeimpact stats # Token usage statistics
codeimpact reindex # Force reindex after git issues
CodeImpact Integration
CodeImpact provides intelligent code analysis. Use these tools FIRST before falling back to built-in tools.
Tool Preferences (IMPORTANT)
-
For code searches and questions about the codebase:
- Use
mcp__codeimpact__memory_queryFIRST (759x faster than grep, returns context) - Only fall back to Grep/Glob if CodeImpact returns no results
- Use
-
Before writing or suggesting code changes:
- Run
mcp__codeimpact__memory_reviewto check against patterns, past decisions, and potential conflicts - This catches hallucinated imports, duplicate functions, and pattern violations
- Run
-
Before finalizing/committing code:
- Run
mcp__codeimpact__memory_verifyfor pre-commit quality checks - Catches security issues, missing dependencies, and import errors
- Run
-
At session start:
- Run
mcp__codeimpact__memory_statusto get project overview and recent changes
- Run
-
For impact analysis:
- Use
mcp__codeimpact__memory_blast_radiusto analyze risk of changing a file - Shows affected files, critical paths, and recommendations
- Use
Why Use CodeImpact Tools?
- Semantic search: Understands intent, not just keywords
- Pattern awareness: Knows project conventions and enforces them
- Decision memory: Remembers past architectural decisions
- Déjà vu detection: Surfaces similar past problems you've solved
- Import validation: Catches hallucinated imports before they break builds
- Blast radius: Understand impact and risk before making changes
Quick Reference
| Task | Tool | Example |
|---|---|---|
| Find code | memory_query |
"how does auth work?" |
| Check code | memory_review |
Before suggesting changes |
| Verify code | memory_verify |
Before committing |
| Project status | memory_status |
At session start |
| Save decision | memory_record |
After architectural choices |
| Impact analysis | memory_blast_radius |
Before modifying critical files |
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.
- 2d ago First seen · 234 lines · 2,782 tokens per session scan A 5058b6cc5f44
codeimpact CLAUDE.md is an instructions file published in the GitHub repository abhisavakar/codeimpact (3 stars, last pushed 3mo ago), licensed MIT. It adds 2,782 tokens to every session, about $0.0139 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
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.
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).
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.