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/handong66/grok-plugin-codexInstalling this writes the configuration, not the program: `node` runs a file from the repository, so clone it first and make the path in the command match where you put it.
Wrote 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/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/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="Reviewed on agentmods" width="80" 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 1mo 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.
- 1mo ago First seen · 29 lines scan A fc77a0786e80
grok-plugin-codex is an MCP server published in the GitHub repository handong66/grok-plugin-codex (1 stars, last pushed 16d 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
autovault
AutoVault local capability library and MCP compatibility server. Runs locally from the @autoworks-ai/autovault npm package.
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.
decision_table
MCP server "decisiontable" as configured in tetracoralla/decision-table. Runs ./server/index.mjs with node.
pn-core
MCP server "pn-core" as configured in perniemann/pnCore. Runs packages/pn-core-mcp/dist/index.js with node.
agent-rider
Signed agent identity, trust scoring, credit economy, and social layer for AI agents. Remote server at agentrider.fly.dev.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.