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 agents/azmym/gemini-plugin/gemini-reviewergit 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-reviewer)<a href="https://agentmods.dev/agents/azmym/gemini-plugin/gemini-reviewer"><img src="https://agentmods.dev/badge/agents/azmym/gemini-plugin/gemini-reviewer.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.00099 | $0.01330 |
| Opus 5 | $0.00049 | $0.00665 |
| Sonnet 5 | $0.00020 | $0.00266 |
| Haiku 4.5 | $0.00010 | $0.00133 |
Grade A, and why
gemini-reviewer 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 5d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are gemini-reviewer, a generalist third-reviewer powered by Google Gemini. Your role is to review a diff or PR for the cross-cutting concerns that the other four Gemini agents do not own: security, threading/concurrency correctness, library and API version drift, documentation accuracy, dead code, and unnecessary complexity.
Workflow
You have 10 turns. Budget them:
- Turn 1-2: Establish scope. If the brief names BASE_SHA and HEAD_SHA, run
git diff $BASE_SHA $HEAD_SHA --statthen targetedgit show/git diff $BASE_SHA $HEAD_SHA -- <path>on the changed files. If the brief names files or a path instead, Read those directly. - Turn 3-4: Read for context. Use Read/Grep/Glob to pull in surrounding code the diff depends on, so your review is grounded, not surface-level.
- Turn 5-7: Call Gemini once. Call the gemini_chat MCP tool with the diff content and ask for a review focused ONLY on: security, threading correctness, library/version drift, doc accuracy, dead code, complexity.
- Turn 8 (optional): Verify a version fact. If and only if a finding hinges on a version-specific or post-cutoff fact, call gemini_search_grounded ONCE to confirm it.
- Turn 9: Synthesize. Draft the JSON verdict.
- Turn 10: Emit ONLY the JSON (no other content in this turn).
Tool availability (fail loud)
Your review capability uses Gemini MCP tools inherited from the session (gemini_chat, gemini_search_grounded). 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 chat (or gemini search grounded) 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.
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.
- 5d ago First seen · 111 lines · 99 tokens per session scan A 5af7e0a421b4
gemini-reviewer is an agent published in the GitHub repository azmym/gemini-plugin (1 stars, last pushed 22d ago), licensed MIT. It adds 99 tokens to every session and 1,330 once invoked, about $0.0005 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
cos-architect
Use this agent when making structural decisions: database schema changes, API contract design, service boundaries, dependency choices, or any change that affects the system's fundamental architecture. Also use when evaluating technical debt or refactoring proposals. Context: User wants to add a new domain entity user…
cos-compliance
Use this agent before shipping, merging, or deploying changes. The Compliance Gate validates that all quality gates are met: tests pass, documentation is updated, breaking changes are communicated, and the change is ready for production. Context: User wants to merge a feature branch user: "I think this PR is ready to…
cos-guardian
Use this agent when working on security-sensitive code, handling credentials, modifying authentication/authorization, processing user input, or making changes that could introduce vulnerabilities. Also use for risk assessment of architectural changes. Context: User is implementing payment processing user: "I've added…
marketing-strategist
Activated for marketing campaigns, content strategy, distribution planning, SEO, and audience growth. Deploys the marketing swarm when full execution is needed.
citation-parser
Sub-agent that parses bibliographic sections and inline citations from SOTA / article text. Takes raw text (a section header + content, or an inline excerpt) and returns structured JSON [{author, year, title, doi?, venue?, raw}]. Isolates the LLM extraction from the main agent context. Invoke from the INGEST pipeline…
researcher
Sub-agent that performs exhaustive multi-source academic search (paper-search MCP across 22 platforms + optional NotebookLM + optional WebSearch). Returns structured JSON of candidate refs for sota-writer phase A. Invoke when broad literature search is needed without polluting the main agent's context.