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 zachdunn/grok-plugin-claude-code/plugin install grok-ccWrote 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/commands/zachdunn/grok-plugin-claude-code/setup)<a href="https://agentmods.dev/commands/zachdunn/grok-plugin-claude-code/setup"><img src="https://agentmods.dev/badge/commands/zachdunn/grok-plugin-claude-code/setup/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/commands/zachdunn/grok-plugin-claude-code/setup"><img src="https://agentmods.dev/badge/commands/zachdunn/grok-plugin-claude-code/setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00018 | $0.00207 |
| Opus 5.5 | $0.00007 | $0.00083 |
| Sonnet 5.5 | $0.00004 | $0.00041 |
| Haiku 4.5 | $0.00002 | $0.00021 |
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 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
Run:
node "${CLAUDE_PLUGIN_ROOT}/scripts/grok-companion.mjs" setup
Then present the result to the user:
- If it reports the binary as NOT FOUND, tell the user Grok is not installed and show the install hint from the output. Do not attempt the install yourself unless the user asks.
- If it reports
authenticated: no, tell the user to run! grok login(the!runs it in their session so the interactive sign-in works), then re-run this command. - If it reports Grok is ready, confirm that
/grok-cc:rescueand thegrok-rescuesubagent are good to go.
Do not run any task or delegation as part of setup — this command only checks readiness.
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 · 20 lines · 18 tokens per session scan A 4f343ae79dd0
setup is a command published in the GitHub repository zachdunn/grok-plugin-claude-code (32 stars, last pushed 4mo ago), licensed MIT. It adds 18 tokens to every session and 207 once invoked, about $0.0001 per session on Opus 5.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
login
Sign in to Grok Build CLI using the default install path.
rescue
Hand a question or code review to xAI's Grok via the grok-consult subagent.
analyze-context
USE WHEN you want to analyze project context before starting work on a task. Calls context + recall, then synthesizes goals, decisions, gotchas, and relevant memories into a pre-task brief.
incident
Live incident response — intake a Sentry issue, stack trace, or symptom; gate mitigate-first vs root-cause-first; keep a UTC timeline. Use when production is broken RIGHT NOW; for the after-action write-up alone, use /orc:postmortem.
bug-check
Run automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.
inspect
Show the configuration Grok discovers for this directory.