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 kai-wedekind/claude-code-grok-bridge/plugin install grok-buildWrote 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/kai-wedekind/claude-code-grok-bridge/check)<a href="https://agentmods.dev/commands/kai-wedekind/claude-code-grok-bridge/check"><img src="https://agentmods.dev/badge/commands/kai-wedekind/claude-code-grok-bridge/check/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/kai-wedekind/claude-code-grok-bridge/check"><img src="https://agentmods.dev/badge/commands/kai-wedekind/claude-code-grok-bridge/check.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.00015 | $0.00384 |
| Opus 5.5 | $0.00006 | $0.00154 |
| Sonnet 5.5 | $0.00003 | $0.00077 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
check 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-bridge.mjs" check --json $ARGUMENTS
If the result says Grok is unavailable:
- Do not invent an install path. Tell the user to install the Grok Build CLI and ensure
grokis on PATH (or setGROK_BINARY). - Then rerun
/grok-build:checkafter they install it.
If Grok is already installed:
- Do not ask about installation.
Optional flags, both of which cost something and are therefore off by default:
--verify-toolsasks the CLI whether it still recognises every id in the read-only removal list. It has to start a real session, which spends real allowance.--fetch-updateasks GitHub for the latest release now, instead of reporting the cached answer. One unauthenticated request; the cache otherwise refreshes from the SessionEnd hook, at most every six hours after a success and on a backoff after a failure.
Output rules:
- Present the final check output to the user.
- If Grok is installed but not authenticated, preserve the guidance to authenticate (for example complete login via interactive
grok, then verify withgrok models). - Present the
Version:line verbatim. Never summariseupdate: unknownas "up to date" — unknown means the check could not run or has never run, and reporting it as current is the one outcome worse than silence, because it stops the user looking. If the user wants a definitive answer, run--fetch-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 · 28 lines · 15 tokens per session scan A 876f7e6cdb56
check is a command published in the GitHub repository kai-wedekind/claude-code-grok-bridge (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 15 tokens to every session and 384 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-31.
Other commands, from other repositories
login
Sign in to Grok Build CLI using the default install path.
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.
me-figure-discussion
Write or review thermal-fluid figure discussion with observation, physical mechanism, comparison, uncertainty, and claim limits.
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.
trace
Export a Grok session trace locally, or upload it to xAI.