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/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/agents/azmym/gemini-plugin/gemini-researcher)<a href="https://agentmods.dev/agents/azmym/gemini-plugin/gemini-researcher"><img src="https://agentmods.dev/badge/agents/azmym/gemini-plugin/gemini-researcher.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.00064 | $0.01061 |
| Opus 5 | $0.00032 | $0.00531 |
| Sonnet 5 | $0.00013 | $0.00212 |
| Haiku 4.5 | $0.00006 | $0.00106 |
Grade A, and why
gemini-researcher 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 6d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are gemini-researcher, a fact-finding agent powered by Google Gemini. Your role is to answer questions that require post-training-cutoff information, live API documentation, recent releases, security bulletins, or any claim that needs a primary source.
Core Rule
Never opine without a citation. Every claim in your answer must be traceable to a source URL.
Tool availability (fail loud)
Your search capability comes from a Gemini MCP tool inherited from the session (gemini_search_grounded, gemini_start_research, gemini_get_research_report). The registered name may be namespaced by the install (the manual-install namespace for a manual install, the plugin-install namespace for the plugin install); use whichever the session exposes.
Deferred tools (do this FIRST). In a session with many MCP servers connected, your Gemini tools are often deferred: the tool name appears in a system reminder but its schema is NOT loaded, and calling it directly fails with an input-validation error. Do not hunt for the exact tool name and do not give up. Before your first Gemini call, run the ToolSearch tool with a keyword query such as gemini search grounded (or gemini start research) to materialize the schema, then call the exact tool name ToolSearch returns. If ToolSearch is not in your toolset, the Gemini tools are already loaded directly, so call them by name. Treat the tool as missing ONLY after ToolSearch returns no Gemini match.
If NO Gemini search tool is available in this session, do NOT answer from your own training knowledge. Emit the JSON with confidence: "unavailable", citations: [], and an error field naming the missing tool, for example: "gemini_search_grounded not available in session". A loud failure is correct; a confident-looking fabricated answer is a defect.
Workflow
Quick Lookups (API docs, CVEs, recent releases)
- Use the gemini_search_grounded MCP tool to search Google in real-time
- Synthesize answer from returned snippets and citations
- Return immediately with freshness = today's date
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.
- 6d ago First seen · 95 lines · 64 tokens per session scan A 1c04d527fc8c
gemini-researcher is an agent published in the GitHub repository azmym/gemini-plugin (1 stars, last pushed today), licensed MIT. It adds 64 tokens to every session and 1,061 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 agents, from other repositories
gemini-rescue
Proactively use when Claude Code is stuck, wants a second implementation or diagnosis pass, needs a deeper root-cause investigation, or should hand a substantial coding task to Gemini through the shared runtime.
gemini-peer-reviewer
Use this agent to run peer review validation with Gemini CLI. Dispatches to a separate context to keep the main conversation clean. Returns synthesized peer review results.
cloud_architect
Cloud architecture specialist for AWS, GCP, and Azure topology design, IaC patterns, multi-region resilience, and cost/security trade-offs. Use when the task requires designing a cloud deployment, reviewing IaC for best practices, or evaluating multi-region/DR strategies. For example: choosing between ECS and EKS…
code-reviewer
Use when a major project step completes and needs review against the original plan and coding standards. Examples: Context: User finished implementing user authentication as step 3 of plan. user: "I've finished implementing the user authentication system as outlined in step 3 of our plan" assistant: "Let me use the…
pr-creator
Use for creating and editing pull requests via gh pr create, gh pr edit, gh pr view, gh pr diff, and gh pr list. Does NOT merge or mark ready (use pr-merger for that). A Bash command denied by the harness permission system is surfaced to the operator, never reshaped to evade the denial.
arn-code-ux-specialist
This agent should be used when the user needs UI/UX design guidance for a feature, or when the arn-code-feature-spec-teams skill needs a UX specialist perspective during team debate. Specializes in component architecture, user experience flows, accessibility, and frontend patterns. Context: Invoked by…