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/commands/lovelaceloom/grok-plugin-cc/ask)<a href="https://agentmods.dev/commands/lovelaceloom/grok-plugin-cc/ask"><img src="https://agentmods.dev/badge/commands/lovelaceloom/grok-plugin-cc/ask/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/commands/lovelaceloom/grok-plugin-cc/ask"><img src="https://agentmods.dev/badge/commands/lovelaceloom/grok-plugin-cc/ask.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.00011 | $0.00277 |
| Opus 5.5 | $0.00004 | $0.00111 |
| Sonnet 5.5 | $0.00002 | $0.00055 |
| Haiku 4.5 | $0.00001 | $0.00028 |
Grade A, and why
ask 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 1mo 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
Forward the user's question to the Grok companion in read-only mode and return the answer verbatim.
Raw user input:
$ARGUMENTS
Run:
node "${CLAUDE_PLUGIN_ROOT}/scripts/companion.mjs" ask "$ARGUMENTS"
Output rules:
- Return the companion's stdout verbatim. Do not paraphrase or summarize.
- If stderr contains a
[hint: ...]line about auth, also surface that hint and suggest/grok:setup. - If
$ARGUMENTSis empty, ask the user what they want Grok to answer instead of running the command.
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.
- 1mo ago First seen · 23 lines · 11 tokens per session scan A c14cff0d0e6b
ask is a command published in the GitHub repository LovelaceLoom/grok-plugin-cc (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 11 tokens to every session and 277 once invoked, about $0.0000 per session on Opus 5.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
ia-verify
Run pre-PR verification chain: build, types, lint, tests, security scan, diff review.
announce
Draft X/Twitter announcement post (or thread) for the latest plugin release.
orchestrate
Do this task as an orchestrator. The aim is the same result at a fraction of the cost: in a long session, every token in this conversation is re-read on each later request, while a subagent's reading is discarded when it returns. The plugin's subagents run on Haiku 5.5, about 40× cheaper per token than Opus 5.5.
release
Generate changelog, bump version, and create git tag.
render
Inspect an archived transcript (gzipped) — show counts, tool calls, errors. Useful after a PreCompact or SessionEnd, before deciding to write a retroactive /continuum:checkpoint.
playbook
Manage Mochi playbooks (list, show, run, delete). Plays through the browser MCP tools.