show

show is a command for Claude Code from kai-wedekind/claude-code-grok-bridge. It costs 15 tokens per session (368 once invoked), scanned A, original, Apache-2.0.

A command for displaying the stored final output of a completed Grok Build run, including its status and result details.

In plain words
What is it for?
Use it to show the latest finished run, inspect a specific run, or wait for one to finish before displaying its output.
Why use it?
It lets you retrieve the actual result of a background job instead of relying only on its run status.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions subagents.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the grok-build plugin — 3 skills, 7 commands, 1 agent, 2 hooks shipped together

Good fit Use it to show the latest finished run, inspect a specific run, or wait for one to finish before displaying its output.

Compare 6 commands from other repositories ↓
Install

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.

Claude Code
/plugin marketplace add kai-wedekind/claude-code-grok-bridge
Claude Code
/plugin install grok-build

Made for: Claude Code.

Or install grok-build, the plugin that ships this one along with the rest of its 3 skills, 7 commands, 1 agent, 2 hooks.

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

agentmods badge for show

README.md
[![agentmods](https://agentmods.dev/badge/commands/kai-wedekind/claude-code-grok-bridge/show.svg)](https://agentmods.dev/commands/kai-wedekind/claude-code-grok-bridge/show)
Your own site
<a href="https://agentmods.dev/commands/kai-wedekind/claude-code-grok-bridge/show"><img src="https://agentmods.dev/badge/commands/kai-wedekind/claude-code-grok-bridge/show.svg" alt="Measured on agentmods" height="20"></a>
Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 368 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00015 $0.00368
Opus 5 $0.00008 $0.00184
Sonnet 5 $0.00003 $0.00074
Haiku 4.5 $0.00002 $0.00037

Measured 7d ago against content hash 0ecd327163c9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

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

plugins/grok-build/commands/show.md · 23 lines

What it actually says

!node "${CLAUDE_PLUGIN_ROOT}/scripts/grok-bridge.mjs" show "$ARGUMENTS"

Behaviour:

  • Without a run id, shows the latest finished run for the current Claude session.
  • With an explicit run id, looks up that id in the workspace (not session-filtered).
  • --wait requires a run id and polls until the run is finished or the wait deadline expires (default 240000 ms; override with --timeout-ms). Wait timeout exits 3 and prints status rather than a result payload.
  • Process exit reflects the stored run status (0 on successful completion, non-zero on failed/cancelled).
  • When Grok fanned out to its own subagents, a Subagents: block lists each strand with its type, status, output size and tool-call count, and warns when any strand produced nothing — a run whose answer rests on two of six strands cost the same as one where all six delivered. --strands prints every strand's full deliverable instead of just the summary.

Present the full command output to the user. Do not summarize or condense it. Preserve all details including:

  • Run ID and status
  • The complete result payload, including verdict, summary, findings, details, artifacts, and next steps
  • File paths and line numbers exactly as reported
  • Any error messages or parse errors
  • Follow-up commands such as /grok-build:runs <id> and /grok-build:review
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.

  1. 7d ago First seen · 23 lines · 15 tokens per session scan A 0ecd327163c9

Subscribe to this mod's changes

show is a command published in the GitHub repository kai-wedekind/claude-code-grok-bridge (2 stars, last pushed 16d ago), licensed Apache-2.0. It adds 15 tokens to every session and 368 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-31.