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 agentmods add commands/faeton/claude-grok-plugin/consultgit clone --depth 1 https://github.com/faeton/claude-grok-pluginWrote 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/commands/faeton/claude-grok-plugin/consult)<a href="https://agentmods.dev/commands/faeton/claude-grok-plugin/consult"><img src="https://agentmods.dev/badge/commands/faeton/claude-grok-plugin/consult.svg" alt="Measured on agentmods" 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 | $0.00016 | $0.00426 |
| Opus 5 | $0.00008 | $0.00213 |
| Sonnet 5 | $0.00003 | $0.00085 |
| Haiku 4.5 | $0.00002 | $0.00043 |
Grade A, and why
consult 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 3d 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
Ask Grok a question via the local companion. Consultation only — Grok runs strictly read-only and cannot edit files; do not act on its answer in this turn.
Raw slash-command arguments:
$ARGUMENTS
Argument shape:
- Everything after
--is the question text. --file <path>(repeatable) attaches a file as context. Resolve paths relative to the current working directory.--model,--effort,--reasoning-effortare passed through to Grok. The companion drops effort flags automatically if the target model does not support them.
If you cannot tell the question from the flags (no -- separator and it is ambiguous), use AskUserQuestion once to clarify.
Execution mode:
- If
$ARGUMENTSincludes--wait, run in the foreground. - If it includes
--background, pass--backgroundto the companion (the companion detaches its own worker; you do NOT need Claude'srun_in_background). - Otherwise default to foreground.
Foreground:
node "${CLAUDE_PLUGIN_ROOT}/scripts/grok-companion.mjs" consult $ARGUMENTS
Return the command stdout verbatim.
Background:
node "${CLAUDE_PLUGIN_ROOT}/scripts/grok-companion.mjs" consult --background $ARGUMENTS
Then tell the user to check /grok:status <id> and /grok:result <id>.
If the companion reports a failure (timeout, stopReason cancellation, or grok not ready), return that message verbatim — do not substitute your own answer.
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.
- 3d ago First seen · 38 lines · 16 tokens per session scan A 02e9f8c883a7
consult is a command published in the GitHub repository faeton/claude-grok-plugin (1 stars, last pushed 19d ago), licensed MIT. It adds 16 tokens to every session and 426 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 commands, from other repositories
implement
Claude plans, Grok implements - write a concrete implementation plan, hand it to Grok as the worker, wait, then verify the result.
review
Run a Grok code review against local git state.
result
Show the stored final output for a finished Grok job in this repository.
transcript
Export the full Grok session transcript for a finished job (or any Grok session ID) as Markdown.
transfer
Transfer the current Claude Code session into a resumable Grok session.
setup
Check whether the local Grok Build CLI is ready and optionally toggle the stop-time review gate.