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/arescope/gemini-plugin-cc/guidenpx skills add arescope/gemini-plugin-cc --skill guidegit clone --depth 1 https://github.com/arescope/gemini-plugin-ccWhat 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.00030 | $0.00611 |
| Opus 5 | $0.00015 | $0.00305 |
| Sonnet 5 | $0.00006 | $0.00122 |
| Haiku 4.5 | $0.00003 | $0.00061 |
Grade A, and why
guide 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gemini Plugin Quick Reference
Commands
| Command | Purpose |
|---|---|
/gemini:review |
Code review with full codebase context |
/gemini:challenge |
Challenge-oriented design review |
/gemini:analyze |
Whole-codebase analysis (1M context) |
/gemini:consult |
Delegate tasks to Gemini |
/gemini:status |
Check background task progress |
/gemini:result |
Get finished task output |
/gemini:cancel |
Stop a running task |
/gemini:setup |
Check install, auth, manage review gate |
Model Aliases
Use with --model on any command:
| Alias | Model |
|---|---|
flash, fast |
gemini-3-flash-preview (default, fastest) |
pro, deep |
gemini-3.1-pro-preview (most capable) |
lite |
gemini-2.5-flash-lite (cheapest) |
flash-2 |
gemini-2.5-flash |
pro-2 |
gemini-2.5-pro |
Effort Levels
Use with --effort on any command (maps to Gemini thinking budget):
| Level | Budget |
|---|---|
low |
Light reasoning |
medium |
Standard |
high |
Deep reasoning |
xhigh, max |
Maximum |
none |
No thinking |
<number> |
Token count |
Review Gate
/gemini:setup --enable-review-gate # Enable
/gemini:setup --disable-review-gate # Disable
/gemini:setup --gate-config model=pro # Configure
Runtime
All commands route through scripts/gemini-companion.mjs. This single entry point handles:
- Model alias resolution
- Effort levels (reserved for future Gemini CLI support)
- Background job tracking (
.gemini-tasks/state.json) - Structured JSON output parsing
- Session lifecycle (SessionStart/SessionEnd hooks)
The stop review gate (hooks/hooks.json) uses Node.js and skips turns that didn't make code edits.
Common Patterns
/gemini:review # Auto-detect scope
/gemini:review --model pro --effort high --base main
/gemini:analyze # Interactive menu
/gemini:consult --model flash --effort low quick fix
/gemini:challenge question the caching design
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 · 77 lines · 30 tokens per session scan A 7241eb5de76c
guide is a skill published in the GitHub repository arescope/gemini-plugin-cc (6 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 30 tokens to every session and 611 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 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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…