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 dashpot4/grok-plugin-for-claude --skill grok-result-handlinggit clone --depth 1 https://github.com/dashpot4/grok-plugin-for-claudeWrote 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/dashpot4/grok-plugin-for-claude/grok-result-handling)<a href="https://agentmods.dev/skills/dashpot4/grok-plugin-for-claude/grok-result-handling"><img src="https://agentmods.dev/badge/skills/dashpot4/grok-plugin-for-claude/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/dashpot4/grok-plugin-for-claude/grok-result-handling"><img src="https://agentmods.dev/badge/skills/dashpot4/grok-plugin-for-claude/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.00018 | $0.00292 |
| Opus 5 | $0.00009 | $0.00146 |
| Sonnet 5 | $0.00004 | $0.00058 |
| Haiku 4.5 | $0.00002 | $0.00029 |
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 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 Result Handling
When a slash command or subagent returns Grok companion output:
- Present the stdout verbatim unless the command instructions say otherwise.
- Do not paraphrase, summarize, or add commentary before or after Grok output for delegate and review commands.
- If the output includes a Grok session ID, preserve it so the user can run
grok resume <session-id>directly. - A normal (foreground) delegate or review returns Grok's answer in-band — present it directly. Do not send the user to
/grok:statusor/grok:resultfor it. - Only for an explicit
--backgroundrun (a detached companion job) tell the user to retrieve the result with/grok:status <id>and/grok:result <id>. - If a foreground delegate was interrupted (for example a very long run hit the Bash ~10-minute limit), its job may be left showing
runningwith no stored result. Tell the user to re-run the task with--background, which survives long runs, rather than waiting on the stuck job. - If setup reports Grok is missing or unauthenticated, direct the user to
/grok:setupor!grok login.
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 · 17 lines · 18 tokens per session scan A af980733aca5
grok-result-handling is a skill published in the GitHub repository dashpot4/grok-plugin-for-claude (4 stars, last pushed 10d ago), licensed Apache-2.0. It adds 18 tokens to every session and 292 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
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.
grok-prompting
Internal guidance for composing clear Grok task prompts from Codex rescue handoffs.
grok-routing
When to reach for Grok Build rather than doing the work in Claude Code — the routing tiers (manual, second-opinion, reach, offload-first, delegate-write), what each one covers, what it costs, and how to call it. Load this before offloading work, before asking for a second opinion, and before delegating anything to…