Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add xzawed/claude-grok-build-plugin/plugin install grokInstalling 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/xzawed/claude-grok-build-plugin/grok-build)<a href="https://agentmods.dev/mcp/xzawed/claude-grok-build-plugin/grok-build"><img src="https://agentmods.dev/badge/mcp/xzawed/claude-grok-build-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/xzawed/claude-grok-build-plugin/grok-build"><img src="https://agentmods.dev/badge/mcp/xzawed/claude-grok-build-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 2mo 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
83% identical to demo-stage — 4 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-build": {
"command": "node",
"args": [
"${CLAUDE_PLUGIN_ROOT}/mcp-server/dist/index.js"
]
}
}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.
- 2mo ago First seen · 8 lines scan A 5b75456fe517
grok-build is an MCP server published in the GitHub repository xzawed/claude-grok-build-plugin (3 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. It is 83% identical to demo-stage, differing in 4 lines, and is treated as a copy.
grok-build compared with mcp servers from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| grok-buildxzawed/claude-grok-build-plugin | MCP server | 3 | 2d ago | MIT | A | — | Claude Code |
| grokVasiHemanth/grok-build-plugin | MCP server | 29 | 1mo ago | Apache-2.0 | A | — | Gemini CLI |
| playwrightnicohodt/claude-code-ui-ux-skill | MCP server | 15 | 2mo ago | MIT | A | — | Claude Code |
| chrome-devtoolsnicohodt/claude-code-ui-ux-skill | MCP server | 15 | 2mo ago | MIT | A | — | Claude Code |
| shadcnnicohodt/claude-code-ui-ux-skill | MCP server | 15 | 2mo ago | MIT | A | — | Claude Code |
| docs-langchainlangchain-ai/langchain | MCP server | 149k | today | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| component-explorermicrosoft/vscode | MCP server | 195k | today | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |