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/dysfunc/ai-plugins-cc/resultgit clone --depth 1 https://github.com/dysfunc/ai-plugins-ccWhat 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.00013 | $0.00168 |
| Opus 5 | $0.00006 | $0.00084 |
| Sonnet 5 | $0.00003 | $0.00034 |
| Haiku 4.5 | $0.00001 | $0.00017 |
Grade A, and why
result 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 2d 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.
This is a copy
81% identical to result — 7 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
!node "${CLAUDE_PLUGIN_ROOT}/scripts/gemini-companion.mjs" result "$ARGUMENTS"
Present the full command output to the user. Do not summarize or condense it. Preserve all details including:
- Job ID and status
- The complete result payload, including verdict, summary, findings, details, artifacts, and next steps
- File paths and line numbers exactly as reported
- Any error messages or parse errors
- Follow-up commands such as
/gemini:status <id>and/gemini:review - Any "transcript truncated" markers from a long resumed thread
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.
- 2d ago First seen · 17 lines · 13 tokens per session scan A c8a13a7cade3
result is a command published in the GitHub repository dysfunc/ai-plugins-cc (4 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 13 tokens to every session and 168 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 81% identical to result, differing in 7 lines, and is treated as a copy.
Other commands, from other repositories
ask
Query multiple AI agents (Gemini, OpenAI, Grok, Perplexity, Kimi, and a local ollama model) for diverse perspectives on architecture decisions, technology choices, debugging dead-ends, and security tradeoffs. Use this whenever the user names the council directly, whatever the topic — ask the council, council review…
result
Fetch, list, or cancel background council jobs started with --async.
status
Check connectivity and configuration status of all council providers.
grok-files
List, prune, or gc Grok (xAI) uploaded files. Cleanup for bridge-owned uploads only.
help
Show how to use deliberation here - what each command does, when to reach for it, and real prompts you can paste right now. Read-only.
setup
Configure deliberation with Codex (GPT), Gemini, Grok, and OpenRouter MCP servers.