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/drhalto/agentmakoWrote 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/drhalto/agentmako/agentmako)<a href="https://agentmods.dev/mcp/drhalto/agentmako/agentmako"><img src="https://agentmods.dev/badge/mcp/drhalto/agentmako/agentmako/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/drhalto/agentmako/agentmako"><img src="https://agentmods.dev/badge/mcp/drhalto/agentmako/agentmako.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
agentmako 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
{
"agentmako": {
"command": "npx",
"args": [
"-y",
"agentmako"
],
"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 8b859bd1209b
agentmako is an MCP server published in the GitHub repository drhalto/agentmako (54 stars, last pushed 2mo 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-30.
Other mcp servers, from other repositories
ctxo
MCP server "ctxo" as configured in alperhankendi/Ctxo. Runs packages/cli/dist/index.js with node.
calm-mcp
MCP server giving coding agents a call-graph-aware, hash-verified view of a codebase, not grep. Runs locally from the @eilodon/calm-mcp npm package.
llm-bus
Coordinate multiple AI agents over MCP: atomic claims, leases, shared ledger, handoffs, tasks. Remote server at mcp.llm-bus.com.
token-pilot
Save up to 80% tokens when AI reads code via AST-aware structural reading. Runs locally from the token-pilot npm package.
oe-mcp
OE MCP Server - connect Claude Code, Cursor & Windsurf to enterprise data sources. One binary, one JSON config. Runs locally from the @openenthrium/oe-mcp npm package.
devpilot-ai
Dev server supervisor for AI coders. Runs locally from the devpilot-ai Python package.