result

result is a command for Claude Code from davit-khaburdzania/grok-plugin-cc. It costs 14 tokens per session (187 once invoked), scanned A, original, Apache-2.0.

A command that displays the complete stored result of a finished Grok job in the repository. Grok is the external review or analysis job referenced by the command.

In plain words
What is it for?
Use it to retrieve a finished job’s status, result payload, changed files, usage details, session information, and next steps.
Why use it?
It lets you inspect the original job output without losing details through summarization, including findings, file locations, errors, and follow-up commands.

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 plugin — 3 skills, 10 commands, 1 agent, 3 hooks shipped together

Good fit Use it to retrieve a finished job’s status, result payload, changed files, usage details, session information, and next steps.

Compare 6 commands from other repositories ↓
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 davit-khaburdzania/grok-plugin-cc
Claude Code
/plugin install grok

Made for: Claude Code.

Or install grok, the plugin that ships this one along with the rest of its 3 skills, 10 commands, 1 agent, 3 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 result

README.md
[![agentmods](https://agentmods.dev/badge/commands/davit-khaburdzania/grok-plugin-cc/result/github.svg)](https://agentmods.dev/commands/davit-khaburdzania/grok-plugin-cc/result)
Your own site
<a href="https://agentmods.dev/commands/davit-khaburdzania/grok-plugin-cc/result"><img src="https://agentmods.dev/badge/commands/davit-khaburdzania/grok-plugin-cc/result/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 result

Your own site · 80×15
<a href="https://agentmods.dev/commands/davit-khaburdzania/grok-plugin-cc/result"><img src="https://agentmods.dev/badge/commands/davit-khaburdzania/grok-plugin-cc/result.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 187 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.00014 $0.00187
Opus 5 $0.00007 $0.00093
Sonnet 5 $0.00003 $0.00037
Haiku 4.5 $0.00001 $0.00019

Measured 9d ago against content hash d3ccaa863d2d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

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

plugins/grok/commands/result.md · 17 lines

What it actually says

!node "${CLAUDE_PLUGIN_ROOT}/scripts/grok-companion.mjs" result "$ARGUMENTS"

Present the full command output to the user. Do not summarize or condense it. Preserve all details including:

  • Job ID and status
  • The complete result payload, including verdict, summary, findings, details, touched files, usage, and next steps
  • File paths and line numbers exactly as reported
  • Any error messages or parse errors
  • The Grok session ID and the grok --resume <session-id> command
  • Follow-up commands such as /grok:status <id>, /grok:transcript <id>, and /grok:review
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. 9d ago First seen · 17 lines · 14 tokens per session scan A d3ccaa863d2d

Subscribe to this mod's changes

result is a command published in the GitHub repository davit-khaburdzania/grok-plugin-cc (1 stars, last pushed 21d ago), licensed Apache-2.0. It adds 14 tokens to every session and 187 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.