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/Walvez/grok-subagentWrote 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/walvez/grok-subagent/grok-subagent-grok-subagent)<a href="https://agentmods.dev/mcp/walvez/grok-subagent/grok-subagent-grok-subagent"><img src="https://agentmods.dev/badge/mcp/walvez/grok-subagent/grok-subagent-grok-subagent/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/walvez/grok-subagent/grok-subagent-grok-subagent"><img src="https://agentmods.dev/badge/mcp/walvez/grok-subagent/grok-subagent-grok-subagent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
grok-subagent 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 9d 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
{
"grok-subagent": {
"command": "node",
"args": [
"./mcp-server/server.mjs"
],
"cwd": "."
}
}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.
- 9d ago First seen · 9 lines scan A 3c1e82203acf
grok-subagent is an MCP server published in the GitHub repository Walvez/grok-subagent (5 stars, last pushed 1mo 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
grok_bridge
MCP server "grokbridge" as configured in conrad85/grok-bridge. Runs ./dist/index.mjs with node.
openspec
MCP server "openspec", hosted remotely at peri-mcpp-gateway.claude-code-best.workers.dev, as configured in KonghaYao/peri.
ip-as-logo
MCP server "ip-as-logo", hosted remotely at peri-mcpp-gateway.claude-code-best.workers.dev, as configured in KonghaYao/peri.
nexfade
MCP server "nexfade" as configured in NexFade/nexfade-grok-plugin. Runs ${GROK_PLUGIN_ROOT}/src/nexfade-mcp.mjs with node. Needs 1 environment variable to run.
codex
MCP server "codex" as configured in jinxlzc/grok-codex-plugin. Runs ${GROK_PLUGIN_ROOT}/scripts/mcp-server.mjs with node.
tokensave
MCP server "tokensave" as configured in inercia/mitto. Launched with /opt/homebrew/bin/tokensave serve.