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 mcp/yywz2026-coder/agentairlock/claude-code-agentairlockgit clone --depth 1 https://github.com/yywz2026-coder/AgentAirlockWrote 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/yywz2026-coder/agentairlock/claude-code-agentairlock)<a href="https://agentmods.dev/mcp/yywz2026-coder/agentairlock/claude-code-agentairlock"><img src="https://agentmods.dev/badge/mcp/yywz2026-coder/agentairlock/claude-code-agentairlock.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
agentairlock 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 4d 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
{
"agentairlock": {
"command": "<ABSOLUTE_NODE_EXE>",
"args": [
"<AGENTAIRLOCK_ROOT>\\integrations\\claude-code\\adapter\\index.mjs",
"--identity-file",
"<AGENTAIRLOCK_ROOT>\\data\\adapters\\claude-code.json"
]
}
}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.
- 4d ago First seen · 10 lines scan A 05e8d9f57501
agentairlock is an MCP server published in the GitHub repository yywz2026-coder/AgentAirlock (0 stars, last pushed 1mo ago), licensed Apache-2.0. 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
openflowkit-mcp
Local-first OpenFlowKit diagramming tools for Claude, Cursor, Windsurf & other MCP clients. Runs locally from the @vrun-design/openflowkit-mcp npm package.
remnic
MCP server "remnic", hosted remotely at localhost, as configured in joshuaswarren/remnic.
flameox
Runtime evidence that helps agents trace, profile, and burn down hotspots in application and native code, GPU kernels, and inference stacks. Runs locally from the flameox Python package.
memorywhale
MCP server "memorywhale" as configured in wuisabel-gif/MemWhale. Launched with mw-mcp.
rag-rat
CLI and MCP entrypoint for indexing repositories into local source, graph, history, and memory evidence. Runs locally from the @rag-rat/bin npm package.
orbit
npm proxy for the Orbit CLI. Downloads the matching native binary from GitHub Releases on install and forwards all invocations. Runs locally from the @orbit-tools/cli npm package.