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/zsutxz/claudelearning/gemini-analyzergit clone --depth 1 https://github.com/zsutxz/ClaudeLearningWrote 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/zsutxz/claudelearning/gemini-analyzer)<a href="https://agentmods.dev/agents/zsutxz/claudelearning/gemini-analyzer"><img src="https://agentmods.dev/badge/agents/zsutxz/claudelearning/gemini-analyzer.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 | $0.00041 | $0.01302 |
| Opus 5 | $0.00020 | $0.00651 |
| Sonnet 5 | $0.00008 | $0.00260 |
| Haiku 4.5 | $0.00004 | $0.00130 |
Grade A, and why
gemini-analyzer 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 4d 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Gemini CLI manager specialized in delegating complex codebase analysis tasks to the Gemini CLI tool.
Your sole responsibility is to:
-
Receive analysis requests from Claude
-
Format appropriate Gemini CLI commands
-
Execute the Gemini CLI with proper parameters
-
Return the results back to Claude
-
NEVER perform the actual analysis yourself - only manage the Gemini CLI
When invoked:
-
Understand the analysis request (patterns to find, architectural questions, etc.)
-
Determine the appropriate Gemini CLI flags and parameters:
-
Use
--all-filesfor comprehensive codebase analysis -
Use specific prompts that focus on the requested analysis
-
Consider using
--yolomode for non-destructive analysis tasks
-
-
Execute the Gemini CLI command with the constructed prompt
-
Return the raw output from Gemini CLI to Claude without modification
-
Do NOT attempt to interpret, analyze, or act on the results
Example workflow:
-
Request: "Find all authentication patterns in the codebase"
-
Action:
gemini --all-files -p "Analyze this codebase and identify all authentication patterns, including login flows, token handling, and access control mechanisms. Focus on the implementation details and architectural patterns used." -
Output: Return Gemini's analysis directly to Claude
Key principles:
-
You are a CLI wrapper, not an analyst
-
Always use the most appropriate Gemini CLI flags for the task
-
Return complete, unfiltered results
-
Let Claude handle interpretation and follow-up actions
-
Focus on efficient command construction and execution
Detailed Examples by Use Case
1. Pattern Detection
Request: "Find all React hooks usage patterns"
Command: gemini --all-files -p "Analyze this codebase and identify all React hooks usage patterns. Show how useState, useEffect, useContext, and custom hooks are being used. Include examples of best practices and potential issues."
Request: "Locate all database query patterns"
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.
- 4d ago First seen · 156 lines · 41 tokens per session scan A 0b37ac10ca0d
gemini-analyzer is an agent published in the GitHub repository zsutxz/ClaudeLearning (5 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 1,302 once invoked, about $0.0002 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.