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/goldmembrane/cleaner-codeWrote 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/goldmembrane/cleaner-code/codesafer)<a href="https://agentmods.dev/mcp/goldmembrane/cleaner-code/codesafer"><img src="https://agentmods.dev/badge/mcp/goldmembrane/cleaner-code/codesafer/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/goldmembrane/cleaner-code/codesafer"><img src="https://agentmods.dev/badge/mcp/goldmembrane/cleaner-code/codesafer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
codesafer 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
{
"codesafer": {
"command": "npx",
"args": [
"-y",
"cleaner-code"
],
"env": {}
}
}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 · 10 lines scan A 76f67a5f55a3
codesafer is an MCP server published in the GitHub repository goldmembrane/cleaner-code (1 stars, last pushed 5mo 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
shellward
AI agent security: 7 MCP tools for injection detection, PII scanning, command safety, DLP. Runs locally from the shellward npm package. Needs 3 environment variables to run.
web-fetcher
MCP server "web-fetcher" as configured in akanthed/SecureAI-Scan. Runs locally from the some-mcp-fetch-server npm package. Needs 1 environment variable to run.
koma-gate-mcp
Classifies prompt injection, jailbreaks, and out-of-scope user input before agents act on it. Runs locally from the koma-gate-mcp npm package. Needs 6 environment variables to run.
plantuml
MCP server for generating PlantUML diagrams. Runs locally from the plantuml-mcp-server npm package. Needs 1 environment variable to run.
aptu-coder
MCP server "aptu-coder" as configured in clouatre-labs/aptu-coder. Launched with https://github.com/clouatre-labs/aptu-coder/releases/download/v0.9.0/aptu-coder-.
mcp
Detect prompt injection, jailbreaks, and code injection in untrusted text before it reaches an LLM. Runs locally from the @safeprompt.dev/mcp npm package. Needs 3 environment variables to run.