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.
npx skills add kai-wedekind/claude-code-grok-bridge --skill grok-run-outputgit clone --depth 1 https://github.com/kai-wedekind/claude-code-grok-bridgeWrote 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/skills/kai-wedekind/claude-code-grok-bridge/grok-run-output)<a href="https://agentmods.dev/skills/kai-wedekind/claude-code-grok-bridge/grok-run-output"><img src="https://agentmods.dev/badge/skills/kai-wedekind/claude-code-grok-bridge/grok-run-output/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/skills/kai-wedekind/claude-code-grok-bridge/grok-run-output"><img src="https://agentmods.dev/badge/skills/kai-wedekind/claude-code-grok-bridge/grok-run-output.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.00018 | $0.00473 |
| Opus 5 | $0.00009 | $0.00236 |
| Sonnet 5 | $0.00004 | $0.00095 |
| Haiku 4.5 | $0.00002 | $0.00047 |
Grade A, and why
grok-run-output 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 11d 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
Grok Build Run Output
When the helper returns Grok output:
- Preserve the helper's verdict, summary, findings, and next steps structure.
- For review or critique output, present findings first and keep them ordered by severity.
- Use the file paths and line numbers exactly as the helper reports them.
- Preserve evidence boundaries. If Grok marked something as an inference, uncertainty, or follow-up question, keep that distinction.
- Preserve output sections when the prompt asked for them, such as observed facts, inferences, open questions, touched files, or next steps.
- If there are no findings, say that explicitly and keep the residual-risk note brief.
- If Grok made edits, say so explicitly and list the touched files when the helper provides them.
- For
grok-build:grok-delegate, do not turn a failed or incomplete Grok run into a Claude-side implementation attempt. Report the failure and stop. - For
grok-build:grok-delegate, if Grok was never successfully invoked, do not generate a substitute answer at all. - CRITICAL: After presenting review or critique findings, STOP. Do not make any code changes. Do not fix any issues. You MUST explicitly ask the user which issues, if any, they want fixed before touching a single file. Auto-applying fixes from a review is strictly forbidden, even if the fix is obvious.
- If the helper reports malformed output or a failed Grok run, include the most actionable stderr lines and stop there instead of guessing. Prefer
failureCodewhen present (no-deliverable,schema-parse,output-truncated,timeout,cli-error,quota-exhausted,not-authenticated). Neitherquota-exhaustednornot-authenticatedis retryable — the first until the allowance resets, the second until somebody signs in. Say that instead of suggesting another attempt, and fornot-authenticatedpass on the remedy the CLI put inrawOutput. - If the helper reports that setup or authentication is required, direct the user to
/grok-build:checkand do not improvise alternate auth flows.
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.
- 11d ago First seen · 22 lines · 18 tokens per session scan A 4f58f6ab376d
grok-run-output is a skill published in the GitHub repository kai-wedekind/claude-code-grok-bridge (2 stars, last pushed 19d ago), licensed Apache-2.0. It adds 18 tokens to every session and 473 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.
Other skills, from other repositories
taiyi-integration
A project workflow skill for closing a TaiyiForge change and recording it in a CHANGELOG.md file. It checks review results, tests, and the state of the working tree before archiving the change.
taiyi-requirement
A requirements-analysis process that turns a proposed change into a REQUIREMENT.md document. It records user needs, acceptance checks, terminology, triggers, and dependencies, with different levels of detail for different project sizes.
taiyi-change
A TaiyiForge workflow stage for writing a change proposal in CHANGE.md, with checks for scope, risks, success criteria, and related project documents.
taiyi-test
A project workflow skill for verifying an implementation and producing a TEST.md record. TDD means writing a failing test, implementing the change, and then making the test pass; this skill checks that process and other regression cases.
taiyi-ui-design
A design-planning guide for describing how an application's user interface should look and behave. It produces a UI-DESIGN.md document covering layouts, components, interactions, accessibility, and error states.
taiyi-diagram-flow
A TaiyiForge diagramming skill that turns requirements and designs into Mermaid workflow diagrams. Mermaid is a text format for drawing flowcharts, API call sequences, and state changes.