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/davit-khaburdzania/grok-plugin-cc/transcriptgit clone --depth 1 https://github.com/davit-khaburdzania/grok-plugin-ccWrote 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/davit-khaburdzania/grok-plugin-cc/transcript)<a href="https://agentmods.dev/commands/davit-khaburdzania/grok-plugin-cc/transcript"><img src="https://agentmods.dev/badge/commands/davit-khaburdzania/grok-plugin-cc/transcript.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.00021 | $0.00134 |
| Opus 5 | $0.00010 | $0.00067 |
| Sonnet 5 | $0.00004 | $0.00027 |
| Haiku 4.5 | $0.00002 | $0.00013 |
Grade A, and why
transcript 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 5d 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
!node "${CLAUDE_PLUGIN_ROOT}/scripts/grok-companion.mjs" transcript "$ARGUMENTS"
Present the command output to the user as-is. It is the Markdown transcript that grok export produced for the session, preceded by the session ID and the grok --resume <session-id> command.
Do not summarize it unless the user asks for a summary.
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.
- 5d ago First seen · 12 lines · 21 tokens per session scan A 0604318a204f
transcript is a command published in the GitHub repository davit-khaburdzania/grok-plugin-cc (1 stars, last pushed 17d ago), licensed Apache-2.0. It adds 21 tokens to every session and 134 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
review
Run a Grok code review against local git state (read-only).
consult
Ask Grok a free-form question, optionally with file context (read-only).
adversarial-review
Run a focused/adversarial Grok review with extra reviewer instructions (read-only).
setup
Check whether the local Grok CLI is installed and authenticated.
export
Export a Grok session transcript as Markdown.
rescue
Hand a question or code review to xAI's Grok via the grok-consult subagent.