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/VasiHemanth/grok-build-pluginWrote 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/plugins/vasihemanth/grok-build-plugin/grok)<a href="https://agentmods.dev/plugins/vasihemanth/grok-build-plugin/grok"><img src="https://agentmods.dev/badge/plugins/vasihemanth/grok-build-plugin/grok/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/plugins/vasihemanth/grok-build-plugin/grok"><img src="https://agentmods.dev/badge/plugins/vasihemanth/grok-build-plugin/grok.svg" alt="Reviewed on agentmods" width="80" 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 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
{
"name": "grok",
"version": "0.1.4",
"description": "Live X/web search, code review, and task delegation via Grok Build. Bundles a grok_search MCP tool usable by any MCP-capable coding agent.",
"author": {
"name": "Grok Plugin Contributors"
}
}
What it installs
The manifest is a name and a version. 1 skill, 7 commands, 1 agent travel with it, and installing the plugin installs all of them — 192 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 9 lines scan A 57bff1f14fcd
grok is a plugin published in the GitHub repository VasiHemanth/grok-build-plugin (30 stars, last pushed 26d ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-30.
Other plugins, from other repositories
pi
Use the Pi coding agent from Claude Code to review code or delegate tasks.
cursor
Local Cursor Agent CLI delegation: multi family consults, Composer implementation in owned worktrees, review, resumable history, background jobs, and setup health checks.
diffgate
A deterministic guardrail your coding agent runs on itself — structured findings on just the changed lines, before the code reaches disk. Zero LLM tokens, 0 false blocks.
grok
Consult xAI's Grok CLI from Claude Code for code review or arbitrary questions.
ai
Umbrella plugin: dispatch /ai:review|rescue|gater across configured providers, plus /ai:compare for fan-out.
gemini
Use Gemini from Claude Code to review code or delegate tasks.