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 skills/gpt-cmdr/ras-commander/dev_invoke_gemini-clinpx skills add gpt-cmdr/ras-commander --skill dev_invoke_gemini-cligit clone --depth 1 https://github.com/gpt-cmdr/ras-commanderWhat 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.00145 | $0.01925 |
| Opus 5 | $0.00072 | $0.00962 |
| Sonnet 5 | $0.00029 | $0.00385 |
| Haiku 4.5 | $0.00015 | $0.00193 |
Grade A, and why
dev_invoke_gemini-cli 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 2d 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 — 295 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Invoking Gemini CLI
Legacy Claude-only orchestration skill. This is not part of the standard production harness policy. It is excluded from the shared multi-harness corpus and should be used only when the user explicitly requests Gemini.
When the user explicitly requests Gemini, delegate the requested review or analysis task to Gemini CLI using markdown files for input and output. Write review criteria to REVIEW.md, invoke Gemini, then read FINDINGS.md for results.
Pattern: Markdown File Handoff
Claude Code Gemini CLI
| |
+-- Write REVIEW.md ----------------+
| (code + review criteria) |
| |
+-- Execute: gemini -y "Read |
| REVIEW.md, analyze, write |
| findings to FINDINGS.md" |
| |
| +-- Reads REVIEW.md
| +-- Analyzes content
| +-- Writes FINDINGS.md
| |
+-- Read FINDINGS.md <--------------+
| (analysis + recommendations) |
v v
Benefits:
- Eliminates shell escaping issues
- Keeps context structured in reviewable files
- Enforces explicit output structure
- Supports session resume
Model Selection
| Model | Use Case | Status |
|---|---|---|
gemini-3-pro-preview |
Default. Strong reasoning | CLI default |
gemini-3-flash-preview |
Large context, fast analysis | For big codebases |
Recommendation: Use default gemini-3-pro-preview for most tasks. Switch to gemini-3-flash-preview for very large context (>100K tokens) via -m flag.
Note: If you encounter 429 capacity errors with gemini-3-pro-preview, retry or wait briefly.
Invocation
Standard Pattern Within This Legacy Skill
cd /path/to/project && gemini -y "Read REVIEW.md in the current directory. Follow the review criteria. Write all findings to FINDINGS.md."
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.
- 2d ago First seen · 295 lines · 145 tokens per session scan A b21b88ee8d9d
dev_invoke_gemini-cli is a skill published in the GitHub repository gpt-cmdr/ras-commander (78 stars, last pushed 2d ago), licensed MIT. It adds 145 tokens to every session and 1,925 once invoked, about $0.0007 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.