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/prgilabert/agent-ecosystem-generator/pr-review-trio-githubgit clone --depth 1 https://github.com/prgilabert/agent-ecosystem-generatorWrote 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/prgilabert/agent-ecosystem-generator/pr-review-trio-github)<a href="https://agentmods.dev/mcp/prgilabert/agent-ecosystem-generator/pr-review-trio-github"><img src="https://agentmods.dev/badge/mcp/prgilabert/agent-ecosystem-generator/pr-review-trio-github.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
github 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 6d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- github — 100% identical, 0 lines differ
What it actually says
{
"github": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-github"
],
"env": {
"GITHUB_TOKEN": "${GITHUB_TOKEN}"
}
}
}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.
- 6d ago First seen · 13 lines scan A 7357ab4fd9d7
github is an MCP server published in the GitHub repository prgilabert/agent-ecosystem-generator (8 stars, last pushed 4mo 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
orchestkit
MCP server "orchestkit" as configured in yonatangross/orchestkit. Runs in Docker (ghcr.io/yonatangross/orchestkit-docs-mcp:9.8.0).
aurora-agent
MCP server "aurora-agent" as configured in AURORA-NEURO/aurora-agent. Launched with ./target/release/bioprism-mcp --root ..
codex-delegate-mcp
Bridge AI coding hosts to the OpenAI Codex CLI for delegated implementation. Runs locally from the codex-delegate-mcp npm package.
june-mcp
MCP server for Junê — give any MCP agent (Claude Desktop, Claude Code, …) a shared, cited knowledge-graph memory backed by a June endpoint. Runs locally from the june-mcp Python package. Needs 13 environment variables to run.
roxy-docs
MCP server "roxy-docs", hosted remotely at roxyapi.com, as configured in RoxyAPI/claude-plugin.
mcp
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps. Runs locally from the @microservices-sh/mcp npm package.