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/JohnXu22786/github-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/johnxu22786/github-mcp/repogate)<a href="https://agentmods.dev/mcp/johnxu22786/github-mcp/repogate"><img src="https://agentmods.dev/badge/mcp/johnxu22786/github-mcp/repogate/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/johnxu22786/github-mcp/repogate"><img src="https://agentmods.dev/badge/mcp/johnxu22786/github-mcp/repogate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
repogate 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
{ "repogate": { "command": "npx", "args": [ "-y", "repogate" ] } }
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 e4fd49a554e2
repogate is an MCP server published in the GitHub repository JohnXu22786/github-mcp (0 stars, last pushed 19d 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
dsh-web-search-free
A locally run web-search provider that can be connected to coding agents such as Claude Code and Codex. It supports a free search option, a paid search option, and two ways for software to connect to it.
opencode-eyes
MCP server "opencode-eyes" as configured in bauerelizabeth07139/opencode-eyes. Runs locally from the opencode-eyes Python package.
opencode-eyes-nvidia
MCP server "opencode-eyes-nvidia" as configured in bauerelizabeth07139/opencode-eyes-nvidia. Runs locally from the opencode-eyes-nvidia Python package.
gpt-dsh-bridge
MCP server "gpt-dsh-bridge" as configured in baochaofan0404/gpt-dsh-bridge. Runs locally from the gpt-dsh-bridge npm package.
deepseek-harness-plugin-mcp
MCP server "deepseek-harness-plugin-mcp" as configured in bobleer/deepseek-harness-plugin-mcp. Runs locally from the deepseek-harness-plugin-mcp npm package.
dsh-vulnerability-remediation-proof
MCP server "dsh-vulnerability-remediation-proof" as configured in dongsheng123132/dsh-vulnerability-remediation-proof. Runs ${pluginDir}/mcp-server.mjs with node.