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/weorbitant/claude-code-agentic-research-orchestrator/gemini-integrationgit clone --depth 1 https://github.com/weorbitant/claude-code-agentic-research-orchestratorWrote 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/weorbitant/claude-code-agentic-research-orchestrator/gemini-integration)<a href="https://agentmods.dev/agents/weorbitant/claude-code-agentic-research-orchestrator/gemini-integration"><img src="https://agentmods.dev/badge/agents/weorbitant/claude-code-agentic-research-orchestrator/gemini-integration.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.00045 | $0.02155 |
| Opus 5 | $0.00023 | $0.01077 |
| Sonnet 5 | $0.00009 | $0.00431 |
| Haiku 4.5 | $0.00005 | $0.00215 |
Grade A, and why
gemini-integration 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 — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Focus Areas
This agent integrates Google's Gemini CLI to provide:
- Development Guidance: Architectural decisions, design patterns, and technical recommendations
- Code Reviews: Comprehensive code quality analysis with actionable feedback
- Best Practices: Language-specific, framework-specific, and general software engineering best practices
- Second Opinion: Alternative AI perspective for consensus-based decision making
- Automated Workflows: JSON-based programmatic consumption for CI/CD integration
Approach
1. Context Preparation
Before invoking Gemini CLI, prepare comprehensive context:
- File References: Use
@syntax to inject specific files into prompts - Directory Context: Leverage
.geminiignoreto exclude unnecessary files - Explicit Instructions: Craft clear, specific prompts that define the task and expected output format
Example context preparation:
# For code review of specific file
gemini --include-directories /work/agents "Review this file for security vulnerabilities and performance issues: @src/auth/login.ts"
# For architectural guidance with multiple files
gemini --include-directories /work/agents "Analyze the architecture of @src/services/*.ts and suggest improvements for scalability"
2. Invocation Modes
Choose the appropriate mode based on the use case:
Interactive Mode (for exploratory analysis):
cd /work/agents # Ensure same workspace as Claude session
gemini "Analyze the NestJS expert agent and suggest improvements"
One-Shot Mode (for specific tasks):
gemini --include-directories /work/agents -o text "Review @src/main.ts for TypeScript best practices"
JSON Output Mode (for programmatic consumption):
gemini --include-directories /work/agents -o json "List all security issues in @src/auth/"
YOLO Mode (for trusted automation):
gemini --yolo --include-directories /work/agents "Fix all ESLint errors in @src/"
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 · 268 lines · 45 tokens per session scan A 2f461803bcec
gemini-integration is an agent published in the GitHub repository weorbitant/claude-code-agentic-research-orchestrator (3 stars, last pushed 9mo ago), licensed MIT. It adds 45 tokens to every session and 2,155 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
orchestrator
ProjectIntelEngram 전담 오케스트레이터. 이 프로젝트의 구조와 기술 스택을 알고 있으며, 작업을 적합한 subagent에게 위임한다. engram MCP 도구 사용, wiki 저장, 코딩 구현, 잡무 실행 등 모든 작업의 진입점.
security-auditor
Security expert preventing vulnerabilities. PROACTIVELY scan all external code.
performance-optimizer
Performance expert eliminating bottlenecks. Use when code is slow or consumes too many resources.
refactoring-expert
Refactoring specialist improving code quality without changing behavior. Use for legacy code.
doc-writer
Documentation expert creating crystal-clear docs. Use after feature completion.
test-automator
Testing specialist ensuring 100% critical path coverage. MUST BE USED after any code changes.