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/yifanyifan897645/git-summary-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/yifanyifan897645/git-summary-mcp/git-summary)<a href="https://agentmods.dev/mcp/yifanyifan897645/git-summary-mcp/git-summary"><img src="https://agentmods.dev/badge/mcp/yifanyifan897645/git-summary-mcp/git-summary/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/yifanyifan897645/git-summary-mcp/git-summary"><img src="https://agentmods.dev/badge/mcp/yifanyifan897645/git-summary-mcp/git-summary.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
git-summary 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
{
"git-summary": {
"command": "npx",
"args": [
"-y",
"git-summary-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 4897b72710e7
git-summary is an MCP server published in the GitHub repository yifanyifan897645/git-summary-mcp (0 stars, last pushed 6mo 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
linebreak-gate
LineBreak security gate at the git/CI boundary: dependency CVE scan + AI SAST, human-approved overrides, git-native audit records. Runs locally from the linebreak-gate Python package.
gitee-mcp-server
MCP Server for using the Gitee API. Runs locally from the gitee-mcp-server npm package.
github-stars
MCP server "github-stars" as configured in 1036007003-wq/github-stars-mcp. Runs locally from the @1036007003-wq/github-stars-mcp npm package. Needs 2 environment variables to run.
p4mcp-server
MCP server "p4mcp-server" as configured in perforce/p4mcp-server. Runs in Docker (ghcr.io/perforce/p4mcp-server:2026.3.2996147). Needs 4 environment variables to run.
telegram-dev
MCP server "telegram-dev" as configured in leshchenko1979/fast-mcp-telegram. Runs src.server with python3.
superskill
One-entry orchestrator for coding agents: jailed vault, FTS knowledge graph, 18-axis review, in-harness Chrome QA. Curated packs — not a 90k-skill dump. Runs locally from the superskill npm package.