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 commands/vasihemanth/grok-build-plugin/setupgit clone --depth 1 https://github.com/VasiHemanth/grok-build-pluginWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00011 | $0.00189 |
| Opus 5 | $0.00005 | $0.00095 |
| Sonnet 5 | $0.00002 | $0.00038 |
| Haiku 4.5 | $0.00001 | $0.00019 |
Grade A, and why
setup 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 2d 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
Run:
node "${CLAUDE_PLUGIN_ROOT}/scripts/grok-companion.mjs" setup --json
Then present a short, friendly summary of the result to the user:
- If
availableis false: tell them the Grok CLI was not found and to install it from https://docs.x.ai (or setGROK_BINto the binary path), then rerun/grok:setup. - If
availableis true butloggedInis false: tell them Grok is installed but not signed in, and to run!grok login, then rerun/grok:setup. - If both are true: confirm Grok is ready and report the account and default model.
Do not run any other commands.
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.
- 2d ago First seen · 20 lines · 11 tokens per session scan A de2784923bcc
setup is a command published in the GitHub repository VasiHemanth/grok-build-plugin (25 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 11 tokens to every session and 189 once invoked, about $0.0001 per session on Opus 5. 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 commands, from other repositories
add-agent
引导新增一个 Agent 适配器。用法 /add-agent.
check
跑全套本地校验(前端 lint/test/build + Rust check)。.
grok_execute
Explicitly turn the task-local Grok executor mode on or off.
grok_init
Discover, verify, and persist the local HTTP proxy used by Grok Build Supervisor.
help
아래 레퍼런스 카드를 사용자에게 그대로 보여주고, 상황에 맞는 다음 한 걸음을 한 줄로 추천하세요 (.oculpm/ 이 없으면 /oculpm:projectinit, 활성 플랜이 있으면 /oculpm:next).
project_init
이 프로젝트를 ocul-pm 추적 대상으로 초기화 (.oculpm/ + 기록 규칙 생성) — 사용자가 직접 실행하는 명시적 시작.