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/skills/lovelaceloom/grok-plugin-cc/grok-ask)<a href="https://agentmods.dev/skills/lovelaceloom/grok-plugin-cc/grok-ask"><img src="https://agentmods.dev/badge/skills/lovelaceloom/grok-plugin-cc/grok-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/skills/lovelaceloom/grok-plugin-cc/grok-ask"><img src="https://agentmods.dev/badge/skills/lovelaceloom/grok-plugin-cc/grok-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.00064 | $0.00687 |
| Opus 5 | $0.00032 | $0.00344 |
| Sonnet 5 | $0.00013 | $0.00137 |
| Haiku 4.5 | $0.00006 | $0.00069 |
Grade A, and why
grok-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 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.
How it starts
The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Grok — Ask
Use this skill when the user asks Grok a question directly, or when you need a second opinion / cross-check from a different model than the one you're running in. The companion script wraps the local grok CLI with environment scrubbing, ANSI sanitization, capability probing, and prompt-injection defenses.
When to use
- The user explicitly asks "ask grok…", "what would grok say about…", "double-check this with grok".
- You want a second perspective from a model with different training (xAI vs OpenAI/Anthropic).
- The question benefits from Grok's strengths: live web/X search awareness, code-focused models, current events.
Do not use this skill for:
- Long-form rescue / multi-step delegation → use the
grok-rescueskill instead. - Image generation → use
grok-imagine. - Deep research that benefits from
--effort max + --checkself-verification → usegrok-research.
How to invoke
Run exactly one bash command:
node "${CLAUDE_PLUGIN_ROOT}/scripts/companion.mjs" ask "<the user's question, properly quoted>"
The CLAUDE_PLUGIN_ROOT env var is set by both Claude Code and Codex CLI. The companion accepts the full argument string and parses its own flags.
Common flags (append to the argument string before the question)
--model <name>— override default Grok model. Available models (run/grok:models):grok-build(default),grok-composer-2.5-fast.--effort <low|medium|high|xhigh|max>— reasoning effort. Note: the current default model (grok-build) declares no reasoning-effort support, so the companion silently strips--effort(with a stderr warning) to avoid a 400 from upstream. It only takes effect on a model that advertisessupports_reasoning_effort.--timeout <duration>— e.g.,90s,5m,0to disable. Default unbounded.--no-web-search— disable Grok's live web search (on by default).--check— append Grok's self-verification loop to the answer.--rules <text|@file>— extra system rules.--sandbox <profile>— restrict tool/filesystem access.
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.
- 9d ago First seen · 46 lines · 64 tokens per session scan A d68cdff0d1f6
grok-ask is a skill published in the GitHub repository LovelaceLoom/grok-plugin-cc (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 64 tokens to every session and 687 once invoked, about $0.0003 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 skills, from other repositories
architect
This skill should be used when the user asks to "design system architecture", "evaluate microservices vs monolith", "create architecture diagrams", "analyze dependencies", "choose a database", "plan for scalability", "make technical decisions", or "review system design".
backend
This skill should be used when the user asks to "design REST APIs", "optimize database queries", "implement authentication", "build microservices", "review backend code", "set up GraphQL", "handle database migrations", or "load test APIs".
ucai-patterns
Use when the user asks about Claude Code best practices, how to write agents, how to use hooks, how to manage context, or how to work effectively with Claude Code's native systems.
frontend-design
Use when user asks to build a web component, page, or application, or when the task involves frontend design, HTML/CSS generation, or UI layout. Applies specific rules for typography, OKLCH color, layout, motion, interaction, and UX writing to produce distinctive, production-grade interfaces that avoid generic AI…
lineage
Use when user invokes /lineage with a column name (optionally qualified with table/schema). Also triggers on "trace this column", "where does X come from", "what reads from Y table". Traces column-level data lineage through SQL, Kafka, Spark, JDBC, and ORM codebases. Produces a structured lineage path with confidence…
explain
Use when user invokes /explain with a file path, directory path, function/class name, or natural language concept. Also triggers on "explain this", "how does X work", "walk me through". Produces a structured, layered explanation of what the code does, how it connects, and where to start if you need to change it. Do…