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 skills add arielaizn/grok-plugin-cc --skill grok-media-resultsgit clone --depth 1 https://github.com/arielaizn/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/skills/arielaizn/grok-plugin-cc/grok-media-results)<a href="https://agentmods.dev/skills/arielaizn/grok-plugin-cc/grok-media-results"><img src="https://agentmods.dev/badge/skills/arielaizn/grok-plugin-cc/grok-media-results/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/arielaizn/grok-plugin-cc/grok-media-results"><img src="https://agentmods.dev/badge/skills/arielaizn/grok-plugin-cc/grok-media-results.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.00078 | $0.00839 |
| Opus 5 | $0.00039 | $0.00419 |
| Sonnet 5 | $0.00016 | $0.00168 |
| Haiku 4.5 | $0.00008 | $0.00084 |
Grade A, and why
grok-media-results 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 12d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reporting Grok media results
A generation that produced a file is not the same as a generation that worked.
Verify before reporting
For images, Read each saved file and actually look at it. Check:
- The subject is what was asked for, not an adjacent thing.
- The composition and aspect ratio match the request.
- Any text in the frame is spelled correctly — this is where image models fail most often.
- For an edit: the requested change happened, and nothing else drifted.
Then report what you saw. If two of four images missed the brief, say which two and how. A user who is told "generated 4 images" and then opens four wrong ones has been given a worse answer than one who was told the truth.
For video, you cannot watch the file. Report the path and size, and say nothing about the motion, pacing, or quality — you do not know. Inventing a description of a clip you cannot see is fabrication, whatever it is dressed up as.
Reading the outcome
The companion exits 0 only when the run produced what was asked for. Exit 2 means something is wrong, and the output says what.
- Completed — files listed, each with its size and the prompt that made it.
- Partial — some files were produced but the run did not finish. Most often a
/grok:videorun whose still frame generated and whose animation step failed. The still is kept and labelled as intermediate. Never present it as the finished video. - Failed — no usable output. The reason is stated; relay it rather than paraphrasing.
Failure modes worth recognising
Zero Data Retention blocking video. HTTP 400 ... Zero Data Retention teams must provide output.upload_url. This is an xAI account setting, not a prompt problem. Retrying fails identically. Relay the explanation and stop — images still work fine, so say that too instead of implying the plugin is broken.
Moderation block. Stop. Tell the user what was blocked and offer a different direction. Do not reword the prompt to evade the filter.
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.
- 12d ago First seen · 55 lines · 78 tokens per session scan A e59bc37d1e89
grok-media-results is a skill published in the GitHub repository arielaizn/grok-plugin-cc (6 stars, last pushed 29d ago), licensed MIT. It adds 78 tokens to every session and 839 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…