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/keshrath/agent-commWrote 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/keshrath/agent-comm/agent-comm)<a href="https://agentmods.dev/mcp/keshrath/agent-comm/agent-comm"><img src="https://agentmods.dev/badge/mcp/keshrath/agent-comm/agent-comm/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/keshrath/agent-comm/agent-comm"><img src="https://agentmods.dev/badge/mcp/keshrath/agent-comm/agent-comm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
agent-comm 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
{
"agent-comm": {
"command": "npx",
"args": [
"-y",
"agent-comm@^1.3.9"
]
}
}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 · 9 lines scan A db303e6602da
agent-comm is an MCP server published in the GitHub repository keshrath/agent-comm (9 stars, last pushed 18d 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
exa
Exa's hosted MCP server: neural web search and page content for the agent. Remote server at mcp.exa.ai.
context7
Context7's hosted MCP server: up-to-date library documentation and code examples on demand. Remote server at mcp.context7.com.
grep_app
MCP server "grepapp", hosted remotely at mcp.grep.app, as configured in sehoon787/my-codex.
dibs
MCP server "dibs" as configured in Agenxy/dibs. Launched with dibs mcp-stdio.
shift-mcp-server
Lightweight coordination layer for multiple AI agents working on the same codebase simultaneously. Runs locally from the @cyanheads/shift-mcp-server npm package. Needs 1 environment variable to run.
deepwiki
DeepWiki's hosted MCP server: AI-generated documentation of public GitHub repositories the agent can query. Remote server at mcp.deepwiki.com.