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/bgreenwell/claude-plugins/gemini-batch-reviewgit clone --depth 1 https://github.com/bgreenwell/claude-pluginsWrote 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/commands/bgreenwell/claude-plugins/gemini-batch-review)<a href="https://agentmods.dev/commands/bgreenwell/claude-plugins/gemini-batch-review"><img src="https://agentmods.dev/badge/commands/bgreenwell/claude-plugins/gemini-batch-review.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.00040 | $0.02666 |
| Opus 5 | $0.00020 | $0.01333 |
| Sonnet 5 | $0.00008 | $0.00533 |
| Haiku 4.5 | $0.00004 | $0.00267 |
Grade A, and why
gemini-batch-review 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 — 445 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/gemini-batch-review Command
Review multiple files or directories with real-time progress tracking and aggregated results.
Syntax
/gemini-batch-review <paths...> [--model flash|pro] [--focus area]
Arguments
paths (required)
- One or more file paths, patterns, or directories
- Space-separated list
- Examples:
src/ tests/,src/**/*.js docs/*.md,src/auth src/api src/services
--model (optional)
- Model to use for review
- Options:
flash(fast, default) orpro(thorough) - Default:
gemini-2.5-flash(recommended for batch)
--focus (optional)
- Specific area to focus review on
- Examples:
security,performance,testing,documentation - Default: General code quality review
How It Works
When user invokes this command:
-
Collect Files
- Expand all paths/patterns to file list
- Filter code files (skip binaries, build artifacts)
- Count total files to review
-
Validate
- Check gemini-cli installed and authenticated
- Verify at least one file found
- Warn if file count is very high (>20 files)
-
Construct Batch Prompt
- Build comprehensive prompt for all files
- Include @ references for each file
- Add focus-specific criteria if specified
-
Execute with Stream-JSON
- Call gemini-cli with
--output-format stream-json - Monitor event stream in real-time
- Track progress through events
- Call gemini-cli with
-
Display Progress
- Show "Starting batch review..."
- Update progress as files are processed
- Display real-time status
-
Aggregate Results
- Collect all findings
- Group by file
- Categorize by severity (errors/warnings)
- Calculate total token usage
-
Present Summary
- File-by-file breakdown
- Overall statistics
- Prioritized recommendations
- Token usage and cost estimate
Examples
Review Multiple Directories
/gemini-batch-review src/ tests/ docs/
Behavior: Reviews all files in src/, tests/, and docs/ with progress
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 · 445 lines · 40 tokens per session scan A 27ea239c14fe
gemini-batch-review is a command published in the GitHub repository bgreenwell/claude-plugins (2 stars, last pushed 8mo ago), licensed MIT. It adds 40 tokens to every session and 2,666 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.