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 zachdunn/grok-plugin-claude-code --skill grok-result-handlinggit clone --depth 1 https://github.com/zachdunn/grok-plugin-claude-codeWrote 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/zachdunn/grok-plugin-claude-code/grok-result-handling)<a href="https://agentmods.dev/skills/zachdunn/grok-plugin-claude-code/grok-result-handling"><img src="https://agentmods.dev/badge/skills/zachdunn/grok-plugin-claude-code/grok-result-handling/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/zachdunn/grok-plugin-claude-code/grok-result-handling"><img src="https://agentmods.dev/badge/skills/zachdunn/grok-plugin-claude-code/grok-result-handling.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.00024 | $0.00372 |
| Opus 5 | $0.00012 | $0.00186 |
| Sonnet 5 | $0.00005 | $0.00074 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
grok-result-handling 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 9d 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 Result Handling
When the grok-companion runtime returns Grok output:
- Preserve the companion's structure: header, summary, findings, and next steps.
- For review output, present findings first, kept in the severity order Grok returned (blocker → high → medium → low → nit). Do not reorder or re-rank.
- Use the
file:linelocations exactly as Grok reports them. - Preserve evidence boundaries. If Grok marked something as an inference, an uncertainty, or an open question, keep that distinction — do not promote an inference to a stated fact.
- Keep the residual-risk note when Grok includes one.
- If there are no findings, say so explicitly and keep the residual-risk note brief. Do not invent issues to fill space.
- If a delegate (
task) run made edits, say so explicitly and list the touched files when Grok reports them. - If a Grok run failed or was incomplete, report the failure and stop. Do not silently turn a failed Grok run into your own Claude-side implementation or a substitute review — the user asked for Grok's work, not a stand-in.
- If Grok was never successfully invoked at all (not installed, not signed in),
say that and point the user at
/grok-cc:setup; do not generate a replacement answer. - A review is read-only. Never apply a fix as part of surfacing review output — if the user wants the fixes made, that is a separate, explicit step.
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.
- 9d ago First seen · 31 lines · 24 tokens per session scan A 41ba89586212
grok-result-handling is a skill published in the GitHub repository zachdunn/grok-plugin-claude-code (30 stars, last pushed 2mo ago), licensed MIT. It adds 24 tokens to every session and 372 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-30.
Other skills, from other repositories
agent-browser
Use the host-side agent-browser CLI for local browser smoke tests, screenshots, snapshots, and simple UI validation against forwarded localhost URLs.
agent-desktop
Use the built-in Computer sub-agent with agent-desktop for macOS desktop automation. Apply when a task needs application launching, accessibility snapshots, stable element refs, window focusing, semantic clicks/typing, or visual confirmation outside the browser sandbox.
grok-brand-media
Prompt recipes for Grok image/video generation from Codex (OG images, README banners, launch clips).
grok-workflows
When and how to run Grok Rhai multi-agent workflows from Codex.
grok-cli-runtime
Internal helper contract for calling the grok-companion runtime from Codex.
grok-routing
When Codex should delegate to Grok vs handle work itself.