A command that displays the final output from a completed Grok job. Grok is an AI service, and a job is a previously submitted piece of work.

Use it to show the latest completed job or retrieve a specific job by its identifier, including the session ID for continuing the work.

It provides a quick way to retrieve completed results without rerunning the job.

result — Command by VasiHemanth

Install

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.

agentmods

npx agentmods add commands/vasihemanth/grok-build-plugin/result

Clone the repo

git clone --depth 1 https://github.com/VasiHemanth/grok-build-plugin

Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 111 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00010	$0.00111
Opus 5	$0.00005	$0.00056
Sonnet 5	$0.00002	$0.00022
Haiku 4.5	$0.00001	$0.00011

Measured yesterday against content hash 9095882d2345, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 yesterday.

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 · 14 lines

What it actually says

Run:

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

Return the companion's stdout verbatim. With no --job, it shows the most recently completed job. The output includes the Grok session id so the user can resume that run directly with grok -r <session-id>.

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.

yesterday First seen · 14 lines · 10 tokens per session scan A 9095882d2345

Subscribe to this mod's changes

result is a command published in the GitHub repository VasiHemanth/grok-build-plugin (25 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 10 tokens to every session and 111 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.

claude-code claude-code-plugin codex coding-agent cursor grok

result

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other commands, from other repositories

add-agent

check

grok_execute

grok_init

help

project_init