Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add TerryCM/vibegroup/plugin install vibegroupWrote 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/terrycm/vibegroup/vibegroup)<a href="https://agentmods.dev/mcp/terrycm/vibegroup/vibegroup"><img src="https://agentmods.dev/badge/mcp/terrycm/vibegroup/vibegroup/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/terrycm/vibegroup/vibegroup"><img src="https://agentmods.dev/badge/mcp/terrycm/vibegroup/vibegroup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
vibegroup 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 10d 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
{
"vibegroup": {
"command": "bun",
"args": [
"${CLAUDE_PLUGIN_ROOT}/dist/channel.js"
]
}
}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.
- 10d ago First seen · 8 lines scan A 344f1a992020
vibegroup is an MCP server published in the GitHub repository TerryCM/vibegroup (11 stars, last pushed 2mo 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-30.
Other mcp servers, from other repositories
mandu
MCP server "mandu" as configured in konamgil/mandu. Launched with bun run packages/mcp/src/index.ts.
ai-crew-sync
MCP server "ai-crew-sync", hosted remotely at bus.your-company.com, as configured in joaquinbejar/ai-crew-sync.
rhizome-mcp
MCP server "rhizome-mcp" as configured in Odrin/rhizome-mcp. Launched with rhizome-mcp serve.
autodemo
Demos-as-code: one run produces video + interactive walkthrough + marketing stills, versioned in git, regenerated by CI, and operable by AI agents via MCP. Runs locally from the @praveen-palanisamy/autodemo npm package.
claude-nexus
MCP server "claude-nexus" as configured in skyvanguard/claude-nexus. Launched with bun ./server.ts.
continuum
A JavaScript (ES6) bytecode virtual machine written in JavaScript. Runs locally from the continuum npm package.