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.
/plugin marketplace add LovelaceLoom/grok-plugin-cc/plugin install grokWrote 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/lovelaceloom/grok-plugin-cc/grok-result-handling)<a href="https://agentmods.dev/skills/lovelaceloom/grok-plugin-cc/grok-result-handling"><img src="https://agentmods.dev/badge/skills/lovelaceloom/grok-plugin-cc/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/lovelaceloom/grok-plugin-cc/grok-result-handling"><img src="https://agentmods.dev/badge/skills/lovelaceloom/grok-plugin-cc/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.00622 |
| Opus 5 | $0.00009 | $0.00311 |
| Sonnet 5 | $0.00004 | $0.00124 |
| Haiku 4.5 | $0.00002 | $0.00062 |
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.
How it starts
The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handling Grok helper output
Use this skill from inside the slash commands and the grok:grok-rescue subagent when forwarding the companion's stdout to the user.
Verbatim contract
Almost everything that comes out of node "${CLAUDE_PLUGIN_ROOT}/scripts/companion.mjs" <sub> should be passed through to the user unchanged. The reasons:
- The user invoked the command in order to see Grok's reasoning.
- Paraphrasing changes verdicts, severity assessments, and concrete fix recommendations.
- Side-by-side comparisons of Grok and Claude reasoning are useful only when both texts are intact.
The verbatim rule applies to:
/grok:ask— answer text from Grok./grok:reviewand/grok:adversarial-review— review findings, including JSON when--jsonis set./grok:rescue— the rescue task output./grok:result— the stored output of a finished job.
What to surface in addition
Augment, do not replace, the verbatim output with these structural cues when they appear in stdout or stderr:
- A
[hint: ...]line on stderr means the companion classified an authentication failure. Show the hint and remind the user to run/grok:setup. - A trailing
[grok-plugin] Job <id> ...line gives a follow-up handle. Keep it so the user can run/grok:status <id>or/grok:result <id>. - A trailing
[grok-plugin] Session: <id> (resume: grok -r <id>)line is a resumption handle for the underlying Grok thread. Keep it visible; some users will want to drop down into the rawgrok -r <id>flow later.
What NOT to do
- Do not collapse multi-finding reviews into a single bullet list.
- Do not strip Grok's reasoning trace ("thought") that may appear inside a
--output-format jsonpayload (the companion already extracts the user-facingtext). - Do not re-run the helper unless the user explicitly asks.
- Do not call
/grok:cancelor/grok:purgeon the user's behalf without explicit instruction.
Failure cases
If the companion exits non-zero or prints a Grok error: line:
- Surface the error verbatim.
- If a
[hint: ...]line is also present, surface that next. - Do not retry. Let the user decide whether to re-run after fixing the underlying issue (auth, quota, etc.).
- Exit code
124specifically means timeout — surface the timeout duration and the--timeout 0escape hatch the companion already prints, but do not silently retry with a longer timeout.
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 · 46 lines · 18 tokens per session scan A dedd741b03db
grok-result-handling is a skill published in the GitHub repository LovelaceLoom/grok-plugin-cc (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 18 tokens to every session and 622 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
architect
This skill should be used when the user asks to "design system architecture", "evaluate microservices vs monolith", "create architecture diagrams", "analyze dependencies", "choose a database", "plan for scalability", "make technical decisions", or "review system design".
backend
This skill should be used when the user asks to "design REST APIs", "optimize database queries", "implement authentication", "build microservices", "review backend code", "set up GraphQL", "handle database migrations", or "load test APIs".
ucai-patterns
Use when the user asks about Claude Code best practices, how to write agents, how to use hooks, how to manage context, or how to work effectively with Claude Code's native systems.
frontend-design
Use when user asks to build a web component, page, or application, or when the task involves frontend design, HTML/CSS generation, or UI layout. Applies specific rules for typography, OKLCH color, layout, motion, interaction, and UX writing to produce distinctive, production-grade interfaces that avoid generic AI…
lineage
Use when user invokes /lineage with a column name (optionally qualified with table/schema). Also triggers on "trace this column", "where does X come from", "what reads from Y table". Traces column-level data lineage through SQL, Kafka, Spark, JDBC, and ORM codebases. Produces a structured lineage path with confidence…
dependabot-sweep
Use when the user wants to fix, address, clear, or resolve open Dependabot security/vulnerability alerts for a repository, end to end. Fetches open alerts via the gh CLI, fixes them per ecosystem (pnpm/npm overrides + lockfile regen, cargo update, pip/go/bundler), verifies with audit and frozen-lockfile installs, then…