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/ellmos-ai/ellmos-codecommander-mcpWrote 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/ellmos-ai/ellmos-codecommander-mcp/ellmos-codecommander-mcp)<a href="https://agentmods.dev/mcp/ellmos-ai/ellmos-codecommander-mcp/ellmos-codecommander-mcp"><img src="https://agentmods.dev/badge/mcp/ellmos-ai/ellmos-codecommander-mcp/ellmos-codecommander-mcp/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/ellmos-ai/ellmos-codecommander-mcp/ellmos-codecommander-mcp"><img src="https://agentmods.dev/badge/mcp/ellmos-ai/ellmos-codecommander-mcp/ellmos-codecommander-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
ellmos-codecommander-mcp 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
{
"ellmos-codecommander-mcp": {
"command": "npx",
"args": [
"-y",
"ellmos-codecommander-mcp"
],
"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 157651e15c4e
ellmos-codecommander-mcp is an MCP server published in the GitHub repository ellmos-ai/ellmos-codecommander-mcp (4 stars, last pushed 2d 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
flyto-indexer
Code intelligence MCP server for AI coding agents with impact analysis, semantic search, dependency graphs, and local release gates. Runs locally from the flyto-indexer Python package.
sonde
Local code graph for TypeScript, Python and Swift: who calls this, what breaks if I change it. Runs locally from the @cheppulabs/sonde npm package.
ferret-mcp
MCP server that extracts complete knowledge from any codebase — architecture, patterns, dependencies, API surface. Runs locally from the ferret-mcp Python package.
code-ast-mcp
MCP server "code-ast-mcp" as configured in m-sameerkhan/code-ast-mcp. Runs locally from the code-ast-mcp Python package.
ripple-impact-mcp
Field-level semantic impact analysis for Claude Code — see the ripple effect of any code change. Runs locally from the ripple-impact-mcp Python package.
cctx-mcp
MCP server for AI agents — structured code analysis that cuts token usage by 87%. Runs locally from the cctx-mcp Python package.