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.
npx agentmods add mcp/bigu1/grok-plugin-codex/grok-grokgit clone --depth 1 https://github.com/bigu1/grok-plugin-codexWrote 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/bigu1/grok-plugin-codex/grok-grok)<a href="https://agentmods.dev/mcp/bigu1/grok-plugin-codex/grok-grok"><img src="https://agentmods.dev/badge/mcp/bigu1/grok-plugin-codex/grok-grok.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
grok 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 4d 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 grok — 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
{
"grok": {
"command": "node",
"args": [
"./mcp/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.
- 4d ago First seen · 9 lines scan A 02b0b87a0028
grok is an MCP server published in the GitHub repository bigu1/grok-plugin-codex (0 stars, last pushed 11d ago), 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. It is 100% identical to grok, differing in 0 lines, and is treated as a copy.
Other mcp servers, from other repositories
codex
MCP server "codex" as configured in jinxlzc/grok-codex-plugin. Runs ${GROK_PLUGIN_ROOT}/scripts/mcp-server.mjs with node.
grok-subagent
MCP server "grok-subagent" as configured in Walvez/grok-subagent. Runs ./mcp-server/server.mjs with node.
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.
grok_bridge
MCP server "grokbridge" as configured in conrad85/grok-bridge. Runs ./dist/index.mjs with node.
grok
MCP server "grok" as configured in stdevMac/grok-in-codex. Runs ./mcp/server.mjs with node.
clawcall
MCP server "clawcall", hosted remotely at api.clawcall.dev, as configured in ClawCall-Dev/ClawCall.