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.
git clone --depth 1 https://github.com/IronAdamant/ChiselWrote 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/mcp/ironadamant/chisel/chisel-test-impact)<a href="https://agentmods.dev/mcp/ironadamant/chisel/chisel-test-impact"><img src="https://agentmods.dev/badge/mcp/ironadamant/chisel/chisel-test-impact/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/ironadamant/chisel/chisel-test-impact"><img src="https://agentmods.dev/badge/mcp/ironadamant/chisel/chisel-test-impact.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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 1mo 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.
What it actually says
{ "chisel-test-impact": { "command": "uvx", "args": [ "chisel-test-impact" ] } }
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.
- 1mo ago First seen · 8 lines scan A b586a4ce138a
chisel-test-impact is an MCP server published in the GitHub repository IronAdamant/Chisel (5 stars, last pushed 3mo 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.
Other mcp servers, from other repositories
promptfoo
TypeScript Execute (tsx): Node.js enhanced with esbuild to run TypeScript & ESM files. Runs locally from the tsx npm package.
slimdex-mcp
Narrow code retrieval for agents: outlines, symbol context, dep graph, persistent memory. Runs locally from the slimdex-mcp npm package.
rendercheck
Assertions for AI-generated media. The bugs don't throw; rendercheck makes them throw. Runs locally from the rendercheck Python package. Needs 1 environment variable to run.
rts
MCP server "rts" as configured in njfio/rs-agent-code-utility. Launched with rts-mcp --workspace ${CLAUDE_PROJECT_DIR:-.}. Needs 2 environment variables to run.
verifyfirst
MCP server for what your verification method cannot see — a registry of software failures that report success. Runs locally from the verifyfirst-mcp Python package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.