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/handong66/grok-plugin-codex/grok-plugin-codex-grok-plugin-codexgit clone --depth 1 https://github.com/handong66/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/handong66/grok-plugin-codex/grok-plugin-codex-grok-plugin-codex)<a href="https://agentmods.dev/mcp/handong66/grok-plugin-codex/grok-plugin-codex-grok-plugin-codex"><img src="https://agentmods.dev/badge/mcp/handong66/grok-plugin-codex/grok-plugin-codex-grok-plugin-codex.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
grok-plugin-codex 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 3d 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-plugin-codex": {
"title": "Grok for Codex",
"description": "Operate Grok CLI with explicit workspace scope and private restart-safe background jobs.",
"cwd": ".",
"command": "node",
"args": [
"./dist/server.js"
],
"env_vars": [
"GROK_BIN",
"GROK_PLUGIN_STATE_DIR",
"HOME",
"PATH",
"XDG_STATE_HOME",
"HTTP_PROXY",
"HTTPS_PROXY",
"ALL_PROXY",
"NO_PROXY",
"http_proxy",
"https_proxy",
"all_proxy",
"no_proxy",
"SSL_CERT_FILE",
"SSL_CERT_DIR",
"NODE_EXTRA_CA_CERTS"
]
}
}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.
- 3d ago First seen · 29 lines scan A fc77a0786e80
grok-plugin-codex is an MCP server published in the GitHub repository handong66/grok-plugin-codex (0 stars, last pushed 2d 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
MCP server "grok" as configured in stdevMac/grok-in-codex. Runs ./mcp/server.mjs with node.
woven
MCP server "woven" as configured in Ducksss/LifeHack-2026. Runs ./node_modules/tsx/dist/cli.mjs with node. Needs 2 environment variables to run.
omnimodal-generation
MCP server "omnimodal-generation" as configured in good-boy4069/Deepseek-omnimodal. Runs locally from the . Python package.
grok-build
MCP server "grok-build" as configured in Reederey87/grok-build-codex-plugin. Launched with /bin/sh ${PLUGIN_ROOT}/mcp-server/bin/grok-build-mcp. Needs 1 environment variable to run.
guarded-notes-mcp
MCP server "guarded-notes-mcp" as configured in nextgencods/guarded-notes-mcp. Runs ./server.mjs with node.
cyberhuatuo
AI-agent self-rescue via MCP: diagnose tracebacks, apply exact fixes, and save/upload reusable prescriptions. Runs locally from the cyberhuatuo Python package.