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 azmym/gemini-plugin --skill gemini-consultgit clone --depth 1 https://github.com/azmym/gemini-pluginWrote 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/azmym/gemini-plugin/gemini-consult)<a href="https://agentmods.dev/skills/azmym/gemini-plugin/gemini-consult"><img src="https://agentmods.dev/badge/skills/azmym/gemini-plugin/gemini-consult.svg" alt="Measured on agentmods" 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.00053 | $0.01150 |
| Opus 5 | $0.00026 | $0.00575 |
| Sonnet 5 | $0.00011 | $0.00230 |
| Haiku 4.5 | $0.00005 | $0.00115 |
Grade A, and why
gemini-consult 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 7d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gemini Consult (dispatch rule)
This skill tells you (the main Claude) WHEN to consult Gemini, WHICH of the five
agents to dispatch, and the cap that keeps consults cheap. It complements
gemini-when-to-use (which routes among the seven capability skills for raw
MCP calls); this skill routes among the five agents for structured,
second-opinion work.
Gemini complements your reasoning. It does not replace it.
When to consult
Dispatch a Gemini agent when ANY of these is true:
- Uncertain about a plausibly post-cutoff fact (library version, API shape, CVE, pricing, changelog). Route to gemini-researcher.
- A specific claim needs external verification before you rely on it. Route to gemini-validator.
- Two or more valid approaches are on the table and you want an outside-the-context-window opinion. Route to gemini-challenger.
- Finalizing a diff or PR for cross-cutting concerns (security, threading, version drift, doc accuracy, dead code, complexity). Route to gemini-reviewer.
- About to compact or hand off a long session and want the state preserved. Route to gemini-summarizer.
Routing table
| Need | Agent |
|---|---|
| Live facts / citations | gemini-researcher |
| Verify a specific claim | gemini-validator |
| Challenge a decision / alternatives | gemini-challenger |
| Generalist diff / PR review | gemini-reviewer |
| Compress session / risk map | gemini-summarizer |
Agents do not call each other (subagents cannot spawn subagents). You are the router: pick the one agent that matches and dispatch it.
Deferred Gemini tools in heavy-MCP sessions
When many MCP servers are connected, Claude Code defers MCP tools: the Gemini
tool names appear in a system reminder, but their schemas are not loaded and a
direct call fails. An agent must call ToolSearch (keyword query such as
gemini search grounded) to materialize the schema before invoking the tool.
The five agents already document this step in their own "Tool availability"
section, so dispatch them normally. But if an agent's JSON comes back with
confidence: "unavailable" / verdict: "unknown" and an error mentioning a
missing Gemini tool, do NOT assume the server is down: first run
/gemini-plugin:gemini-doctor. If doctor's check 2 passes but check 3 fails,
the session is stale (restart Claude Code); if both pass, retry the dispatch.
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.
- 7d ago First seen · 103 lines · 53 tokens per session scan A b091f3bdfef8
gemini-consult is a skill published in the GitHub repository azmym/gemini-plugin (1 stars, last pushed yesterday), licensed MIT. It adds 53 tokens to every session and 1,150 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
grok-prompting
Internal guidance for composing Grok prompts for coding, review, diagnosis, and research tasks inside the Grok Claude Code plugin.
gemini-cli-runtime
Internal helper contract for calling the gemini-companion runtime from Claude Code.
gemini-prompting
Internal guidance for composing effective Gemini prompts for visual analysis, design review, and coding tasks.
gemini-result-handling
Internal guidance for presenting Gemini helper output back to the user.
gemini-peer-review
This skill should be invoked BEFORE presenting implementation plans, architecture recommendations, code review findings, or answers to broad technical questions. Use proactively when about to "recommend", "suggest", "propose", "design", "plan", or answer "how should", "what's the best way", "which approach". MANDATORY…
bionic-decision-engine
Unified mathematical arbitrator for all resource allocation decisions — money, time, energy, relationships. Absorbs 46 decision protocols + 24 strategy protocols into one dense engine.