A setup command that checks whether the local Grok command-line tool is installed and ready to use. It can also turn a review step on or off when the tool supports that option.

Use it before using Grok to check installation and login status, optionally install the command-line tool, or change the stop-time review setting.

It shows whether Grok is available and identifies the next authentication or installation step when it is not ready. This avoids discovering setup problems only when trying to run another command.

setup — Command by LovelaceLoom

Install

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.

agentmods

npx agentmods add commands/lovelaceloom/grok-plugin-cc/setup

Clone the repo

git clone --depth 1 https://github.com/LovelaceLoom/grok-plugin-cc

Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 442 The whole file, excluding the scripts and references it only reads on demand.

Security scan D 3 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00017	$0.00442
Opus 5	$0.00009	$0.00221
Sonnet 5	$0.00003	$0.00088
Haiku 4.5	$0.00002	$0.00044

Measured 2d ago against content hash ded67c532889, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

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

plugins/grok/commands/setup.md · 45 lines

What it actually says

Run:

node "${CLAUDE_PLUGIN_ROOT}/scripts/companion.mjs" setup --json "$ARGUMENTS"

If the result says Grok is unavailable:

Use AskUserQuestion exactly 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 login and 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.json under env. (The legacy GROK_CODE_XAI_API_KEY still works as a fallback.)

Output rules:

Present the parsed setup output as a short status block to the user.
If actionsTaken is non-empty (review gate was toggled, or a fallback model was persisted), surface that.
If nextSteps is non-empty, surface it.
If ready: true and no actions/steps, just confirm success.
If capabilities.ok is false, surface the missing flags and recommend grok update.

Changes

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 · 45 lines · 17 tokens per session scan D ded67c532889

Subscribe to this mod's changes

setup is a command published in the GitHub repository LovelaceLoom/grok-plugin-cc (5 stars, last pushed 24d ago), licensed Apache-2.0. It adds 17 tokens to every session and 442 once invoked, about $0.0001 per session on Opus 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.

Code review Data and AI ai-assistant ai-tools claude-code claude-code-plugin developer-tools

setup

Getting it into your agent

What it costs to keep this loaded

Grade D, and why

Downloads and executes remote codehighSupply chain

Reads agent configuration directoriesmediumAgent snooping

Makes network callslowCapability

What it actually says

What this file has done since we first saw it

Other commands, from other repositories

test-tools

release

spec-audit

spec

implement-audit

implement