What is chisel-test-impact?

A local tool that analyzes which tests are affected by code changes and provides information about the code involved. It is distributed as a Python package.

Use it when assessing the testing impact of a code change or gathering code intelligence for an AI coding agent.

It helps narrow testing to code and tests related to a change, reducing guesswork about what should be checked. The description does not specify its exact commands or output format.

chisel-test-impact — MCP server by IronAdamant

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 mcp/ironadamant/chisel/chisel-test-impact

Clone the repo

git clone --depth 1 https://github.com/IronAdamant/Chisel

Made for: Claude Code, Codex, Cursor.

Per session not measured What this adds to a session before it is invoked.

When invoked not measured Not applicable: nothing here is loaded into a session.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Security

Grade A, and why

chisel-test-impact 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 yesterday.

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.

listed in the official MCP registry · 8 lines

What it actually says

{ "chisel-test-impact": { "command": "uvx", "args": [ "chisel-test-impact" ] } }

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.

yesterday First seen · 8 lines scan A b586a4ce138a

Subscribe to this mod's changes

chisel-test-impact is an MCP server published in the GitHub repository IronAdamant/Chisel (2 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. 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.

Data and AI Git and workflow LLM Testing ai-agents claude-code code-intelligence git-analysis mcp

sem-review

MCP server "sem-review" as configured in Ataraxy-Labs/sem. Launched with ${CLAUDE_PLUGIN_ROOT}/../../crates/target/debug/sem mcp. Needs 2 environment variables to run.

Ataraxy-Labs/sem · not measured

sem

Entity-level code intelligence: semantic diff, impact analysis, blame, and context for AI agents. Runs locally from the @ataraxy-labs/sem npm package.

Ataraxy-Labs/sem · not measured

basemind

MCP server "basemind" as configured in Goldziher/basemind. Runs const fs=require("fs"),p=require("path"),o=require("os"),u=require("url"),c=p.join(process.env.BASEMIND_CODEX_HOME||process.env.CODEX_HOME||p.join(o.homedir(),".codex"),"plugins","cache"),s=fs.readdirSync(c,{withFileTypes:true}).flatMap(m=>{const…

Goldziher/basemind · not measured

chisel-test-impact

Getting it into your agent

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other mcp servers, from other repositories

sem-review

sem

basemind

mache

m1nd

mako-ai