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/caipe-io/ai-platform-engineeringWrote 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/caipe-io/ai-platform-engineering/vscode-github)<a href="https://agentmods.dev/mcp/caipe-io/ai-platform-engineering/vscode-github"><img src="https://agentmods.dev/badge/mcp/caipe-io/ai-platform-engineering/vscode-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 today.
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
{
"github": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"GITHUB_PERSONAL_ACCESS_TOKEN=${github_token}",
"ghcr.io/github/github-mcp-server:latest"
],
"transport": "stdio"
}
}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.
- today First seen · 14 lines scan A cd25e014b69e
github is an MCP server published in the GitHub repository caipe-io/ai-platform-engineering (407 stars, last pushed today), licensed Apache-2.0. 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-09-06.
Other mcp servers, from other repositories
worldlines
MCP server "worldlines", hosted remotely at 127.0.0.1, as configured in LudicDynamics/WorldLines.
landlord-framework
MCP server "landlord-framework" as configured in DizzyMii/landlord. Runs locally from the landlord-framework Python package.
multi-agent-orchestration-with-mcp-and-a2a
MCP server "multi-agent-orchestration-with-mcp-and-a2a" as configured in Saad-Dev13/MultiAgentOrchestrationwithMCPandA2A. Runs locally from the multi-agent-orchestration-with-mcp-and-a2a Python package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
reference-langchain
MCP server "reference-langchain", hosted remotely at reference.langchain.com, as configured in langchain-ai/langchain.
mcp-search
MCP server "mcp-search" as configured in thedotmack/claude-mem. Runs const f=require('fs'),p=require('path'),o=require('os'),c=require('child_process');const h=o.homedir();const C=process.env.CLAUDE_CONFIG_DIR||p.join(h,'.claude');const E=process.env.CLAUDE_PLUGIN_ROOT||process.env.PLUGIN_ROOT||'';const…