code-impact-mcp CLAUDE.md

Instructions for a TypeScript MCP server that maps imports and exports in a JavaScript or TypeScript project to show which files may be affected by a change. A dependency graph records those relationships.

In plain words
What is it for?
Use them when building, testing, linting, smoke-testing, releasing, or changing its dependency-impact and cycle-detection analysis.
Why use it?
They provide the commands, architecture, release files, and design limits needed to develop and publish the tool correctly.

Instructions file

Install

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.

agentmods
npx agentmods add instructions/vk0dev/code-impact-mcp/claude-md
Clone the repo
git clone --depth 1 https://github.com/vk0dev/code-impact-mcp
Per session 390 This file is loaded in full into every session.
When invoked 390 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00390 $0.00390
Opus 5 $0.00195 $0.00195
Sonnet 5 $0.00078 $0.00078
Haiku 4.5 $0.00039 $0.00039

Measured 2d ago against content hash 67eba85665a4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

code-impact-mcp 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.

CLAUDE.md · 33 lines

What it actually says

@vk0/code-impact-mcp

Dependency graph and blast-radius analysis for agent-driven code changes. Predicts what breaks before you commit.

Stack

  • TypeScript, @modelcontextprotocol/sdk, Zod, ts-morph
  • Vitest for unit tests

Commands

  • Install: npm ci
  • Build: npm run build
  • Test: npm test
  • Lint: npm run lint
  • Smoke test: npm run smoke

Publishing

  • See PUBLISHING.md for full marketplace playbook
  • Version sync: package.json, .claude-plugin/plugin.json, server.json, src/createServer.ts
  • Release: git tag -a vX.Y.Z && git push --follow-tags → CI publishes to npm + MCP Registry + Smithery

Architecture

  • src/createServer.ts — McpServer factory, exports createServer() and createSandboxServer() (Smithery)
  • src/server.ts — CLI/stdio entry point, uses createServer()
  • src/index.ts — Barrel exports for library usage
  • src/tools/index.ts — 4 MCP tools registration
  • src/graph.ts — ts-morph dependency graph builder, impact analysis, cycle detection

Notes

  • Analyzes TS/JS projects by parsing import/export relationships with ts-morph
  • Graph is cached per (projectRoot, tsconfigPath) pair
  • Local-first, zero network egress
  • Verification note: npm test exits cleanly on a clean/stashed tree. If tracked runtime/test files like src/graph.ts or tests/graph.test.ts are left dirty from another lane, isolate them with git stash before QA so you do not misread a dirty-worktree timeout/regression as a repo-wide vitest exit bug.
Changes

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.

  1. 2d ago First seen · 33 lines · 390 tokens per session scan A 67eba85665a4

Subscribe to this mod's changes

code-impact-mcp CLAUDE.md is an instructions file published in the GitHub repository vk0dev/code-impact-mcp (1 stars, last pushed 8d ago), licensed MIT. It adds 390 tokens to every session, about $0.0019 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.

Related

Other instructions, from other repositories