agentmods.dev

runs

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

A command for listing active and recent Grok Build runs, which are background jobs that build or process something for a repository.

In plain words
What is it for?
Use it to list runs, include older runs from all Claude sessions, or wait for a specific run to finish.
Why use it?
It gives you a compact view of run status and history when you need to find an ongoing job or understand what happened to an earlier one.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

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

not rated 2repo 2mo ago A scan 11 tokens original Apache-2.0

Good fit Use it to list runs, include older runs from all Claude sessions, or wait for a specific run to finish.

Compare 6 commands from other repositories ↓
View source ↗ kai-wedekind/claude-code-grok-bridge
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 runs

README.md
[![agentmods](https://agentmods.dev/badge/commands/kai-wedekind/claude-code-grok-bridge/runs/github.svg)](https://agentmods.dev/commands/kai-wedekind/claude-code-grok-bridge/runs)
Your own site
<a href="https://agentmods.dev/commands/kai-wedekind/claude-code-grok-bridge/runs"><img src="https://agentmods.dev/badge/commands/kai-wedekind/claude-code-grok-bridge/runs/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.

agentmods 80×15 button for runs

Your own site · 80×15
<a href="https://agentmods.dev/commands/kai-wedekind/claude-code-grok-bridge/runs"><img src="https://agentmods.dev/badge/commands/kai-wedekind/claude-code-grok-bridge/runs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 410 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.00011 $0.00410
Opus 5.5 $0.00004 $0.00164
Sonnet 5.5 $0.00002 $0.00082
Haiku 4.5 $0.00001 $0.00041

Measured 1mo ago against content hash 2a62d6b18119, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

plugins/grok-build/commands/runs.md · 26 lines

What it actually says

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

Session scope (do not invent a missing-history explanation):

  • Default list is scoped to the current Claude session (GROK_CC_SESSION_ID). Finished runs from earlier sessions stay on disk but are hidden by that filter.
  • --all keeps the current-session filter but does not cap the recent-finished list at 8.
  • --all-sessions lists every run in this workspace across Claude sessions (and adds a Claude Session column). Use this when the user asks about history from a previous session or says runs "disappeared".
  • SessionEnd cancels active runs for the ending session; it does not delete job records. Retention is MAX_JOBS pruning (50) plus optional bridge clean.
  • --wait requires a run id. Wait timeout exits 3 while the job is still active.

If the user did not pass a run ID:

  • Render the command output as a single Markdown table for the current and past runs in this session (or all sessions if --all-sessions was passed).
  • Keep it compact. Do not include progress blocks or extra prose outside the table.
  • Preserve the actionable fields from the command output, including run ID, kind, status, phase, elapsed or duration, summary, and follow-up commands.
  • If the table is empty and the user expected history, mention /grok-build:runs --all-sessions once.

If the user did pass a run ID:

  • Present the full command output to the user.
  • Do not summarize or condense it.
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. 1mo ago First seen · 26 lines · 11 tokens per session scan A 2a62d6b18119

Subscribe to this mod's changes

runs 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 11 tokens to every session and 410 once invoked, about $0.0000 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.

Claude Codeai-agentsapache-2-0developer-toolsgrokplugin
Related

Other commands, from other repositories

login

Sign in to Grok Build CLI using the default install path.

dashpot4/grok-plugin-for-claude · 12 tokens

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.

RohiRIK/OpenLtm · 39 tokens

me-figure-discussion

Write or review thermal-fluid figure discussion with observation, physical mechanism, comparison, uncertainty, and claim limits.

hanhuark/mechanical-engineering-research-skill · 21 tokens

bug-check

Run automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.

yeaight7/agent-powerups · 25 tokens

inspect

Show the configuration Grok discovers for this directory.

xzawed/claude-grok-build-plugin · 9 tokens

trace

Export a Grok session trace locally, or upload it to xAI.

xzawed/claude-grok-build-plugin · 14 tokens