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 LovelaceLoom/grok-plugin-cc/plugin install grokWrote 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/lovelaceloom/grok-plugin-cc/setup)<a href="https://agentmods.dev/commands/lovelaceloom/grok-plugin-cc/setup"><img src="https://agentmods.dev/badge/commands/lovelaceloom/grok-plugin-cc/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/lovelaceloom/grok-plugin-cc/setup"><img src="https://agentmods.dev/badge/commands/lovelaceloom/grok-plugin-cc/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.00017 | $0.00442 |
| Opus 5.5 | $0.00007 | $0.00177 |
| Sonnet 5.5 | $0.00003 | $0.00088 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade D, and why
setup scanned grade D with 3 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -fsSL https://x.ai/cli/install.sh | bash Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
2. Set `XAI_API_KEY` (get a key from https://console.x.ai) — either inline (`export XAI_API_KEY=...`) or in `~/.claude/settings.json` under `env`. (The legacy `GROK_CODE_XAI_API_KEY` still works as a fallback.) Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
allowed-tools: Bash(node:*), Bash(curl:*), AskUserQuestion What it actually says
Run:
node "${CLAUDE_PLUGIN_ROOT}/scripts/companion.mjs" setup --json "$ARGUMENTS"
If the result says Grok is unavailable:
- Use
AskUserQuestionexactly once to ask whether Claude should install Grok now. - Put the install option first and suffix it with
(Recommended). - Use these two options:
Install Grok CLI (Recommended)Skip for now
- If the user chooses install, run:
curl -fsSL https://x.ai/cli/install.sh | bash
- Then rerun:
node "${CLAUDE_PLUGIN_ROOT}/scripts/companion.mjs" setup --json "$ARGUMENTS"
If Grok is already installed:
- Do not ask about installation.
If Grok is installed but not authenticated, the JSON nextSteps will spell out the two options. Present them to the user verbatim. The two valid options are:
- Run
!grok loginand complete the browser OAuth flow. - Set
XAI_API_KEY(get a key from https://console.x.ai) — either inline (export XAI_API_KEY=...) or in~/.claude/settings.jsonunderenv. (The legacyGROK_CODE_XAI_API_KEYstill works as a fallback.)
Output rules:
- Present the parsed setup output as a short status block to the user.
- If
actionsTakenis non-empty (review gate was toggled, or a fallback model was persisted), surface that. - If
nextStepsis non-empty, surface it. - If
ready: trueand no actions/steps, just confirm success. - If
capabilities.okis false, surface the missing flags and recommendgrok update.
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 · 45 lines · 17 tokens per session scan D ded67c532889
setup is a command published in the GitHub repository LovelaceLoom/grok-plugin-cc (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 442 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it D with 3 findings (downloads and executes remote code, reads agent configuration directories, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
ia-verify
Run pre-PR verification chain: build, types, lint, tests, security scan, diff review.
announce
Draft X/Twitter announcement post (or thread) for the latest plugin release.
orchestrate
Do this task as an orchestrator. The aim is the same result at a fraction of the cost: in a long session, every token in this conversation is re-read on each later request, while a subagent's reading is discarded when it returns. The plugin's subagents run on Haiku 5.5, about 40× cheaper per token than Opus 5.5.
release
Generate changelog, bump version, and create git tag.
render
Inspect an archived transcript (gzipped) — show counts, tool calls, errors. Useful after a PreCompact or SessionEnd, before deciding to write a retroactive /continuum:checkpoint.
playbook
Manage Mochi playbooks (list, show, run, delete). Plays through the browser MCP tools.