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.
git clone --depth 1 https://github.com/dysfunc/ai-plugins-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/plugins/dysfunc/ai-plugins-cc/grok)<a href="https://agentmods.dev/plugins/dysfunc/ai-plugins-cc/grok"><img src="https://agentmods.dev/badge/plugins/dysfunc/ai-plugins-cc/grok/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/plugins/dysfunc/ai-plugins-cc/grok"><img src="https://agentmods.dev/badge/plugins/dysfunc/ai-plugins-cc/grok.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
grok 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
{
"name": "grok",
"version": "1.0.0",
"description": "Use Grok from Claude Code to review code or delegate tasks.",
"author": {
"name": "xAI"
}
}
What it installs
The manifest is a name and a version. 3 skills, 1 agent travel with it, and installing the plugin installs all of them — 102 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 9 lines scan A 45261ed00558
grok is a plugin published in the GitHub repository dysfunc/ai-plugins-cc (4 stars, last pushed 5mo ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
claude-council
Consult multiple AI coding agents (Gemini, OpenAI, Grok, Perplexity, Kimi, any model OpenRouter routes to, plus codex, antigravity, grok, kimi and cursor CLIs when installed, and a local ollama model) to get diverse perspectives on coding problems, with a streaming pane in tmux or inside Claude Code. It can also hand…
deliberation
Use when you want a delegated second opinion or implementation from GPT (Codex), Gemini, Grok (xAI), or OpenRouter (config-driven, 400+ models) - seven expert subagents (Architect, Plan Reviewer, Scope Analyst, Code Reviewer, Security Analyst, Researcher, Debugger) and bundled…
grok
Live X/web search, code review, and task delegation via Grok Build. Bundles a groksearch MCP tool usable by any MCP-capable coding agent.
cursor
Local Cursor Agent CLI delegation: multi family consults, Composer implementation in owned worktrees, review, resumable history, background jobs, and setup health checks.
gemini
Gemini via Antigravity CLI for Claude Code — ask, review, adversarial-review, implement.
gemini
Use Gemini CLI from Claude Code to review code or delegate tasks.