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/Reederey87/grok-build-codex-pluginInstalling this writes the configuration, not the program: `/bin/sh` has to be on your PATH already, or the server will not start.
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/reederey87/grok-build-codex-plugin/grok-build)<a href="https://agentmods.dev/mcp/reederey87/grok-build-codex-plugin/grok-build"><img src="https://agentmods.dev/badge/mcp/reederey87/grok-build-codex-plugin/grok-build/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/reederey87/grok-build-codex-plugin/grok-build"><img src="https://agentmods.dev/badge/mcp/reederey87/grok-build-codex-plugin/grok-build.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
grok-build 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- grok-build — 100% identical, 0 lines differ
What it actually says
{
"grok-build": {
"command": "/bin/sh",
"args": [
"${PLUGIN_ROOT}/mcp-server/bin/grok-build-mcp"
],
"env": {
"GROK_BUILD_API_FALLBACK": "false"
}
}
}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 · 11 lines scan A d1ef22702fd6
grok-build is an MCP server published in the GitHub repository Reederey87/grok-build-codex-plugin (5 stars, last pushed 22d 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. 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
govreposcrape
MCP server "govreposcrape", hosted remotely at govreposcrape-api-1060386346356.us-central1.run.app, as configured in tractorjuice/arckit-codex.
uk-tenders
MCP server "uk-tenders", hosted remotely at tenders.run.cns.me, as configured in tractorjuice/arckit-codex.
tapd-requirement
MCP server "tapd-requirement" as configured in skyloevil/codex-sdd. Runs ./scripts/tapd-mcp-server.mjs with node. Needs 1 environment variable to run.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
component-explorer
MCP server "component-explorer" as configured in microsoft/vscode. Launched with npm exec --no -- component-explorer mcp -p ./test/componentFixtures/component-ex.
vscode-automation-mcp
MCP server "vscode-automation-mcp" as configured in microsoft/vscode. Launched with npm --prefix test/mcp run start-stdio.