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/kyopark2014/agent-pluginsWrote 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/kyopark2014/agent-plugins/enterprise-search-guru)<a href="https://agentmods.dev/mcp/kyopark2014/agent-plugins/enterprise-search-guru"><img src="https://agentmods.dev/badge/mcp/kyopark2014/agent-plugins/enterprise-search-guru.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
guru 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 8d 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.
This is a copy
100% identical to guru — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"guru": {
"type": "http",
"url": "https://mcp.api.getguru.com/mcp"
}
}What else .mcp.json configures
This page is one entry in a file that holds 8. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 8d ago First seen · 6 lines scan A e493cc48842c
guru is an MCP server published in the GitHub repository kyopark2014/agent-plugins (4 stars, last pushed today), 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. It is 100% identical to guru, differing in 0 lines, and is treated as a copy.
Other mcp servers, from other repositories
ruflo
MCP server "ruflo" as configured in martineserios/thebrana. Launched with ${HOME}/enter_thebrana/thebrana/system/scripts/ruflo-mcp.sh mcp start. Needs 1 environment variable to run.
cgr-capture
MCP server that captures agent judgments and outcomes as CGR substrate on GRAFOMEM Cloud. Runs locally from the grafomem-cgr Python package. Needs 6 environment variables to run.
cgr-read
Read Foundation-signed, offline-verifiable CGR agent-reputation attestations. No install. Remote server at mcp.grafomem.com.
yaps
MCP server "yaps" as configured in richawo/yaps-codex-plugin. Runs ./mcp/server/index.mjs with node. Needs 6 environment variables to run.
clawsouls
ClawSouls MCP Server — SoulScan, Soul Rollback, Swarm Memory, Persona Search & Install for AI agents. Runs locally from the clawsouls-mcp npm package.
portable-agent-memory
MCP server "portable-agent-memory" as configured in skywaller0/Portable-Agent-Memory. Runs locally from the portable-agent-memory Python package.