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/gemini-cli-runtimenpx skills add arescope/gemini-plugin-cc --skill gemini-cli-runtimegit 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.00017 | $0.00340 |
| Opus 5 | $0.00009 | $0.00170 |
| Sonnet 5 | $0.00003 | $0.00068 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
gemini-cli-runtime 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.
What it actually says
Gemini CLI Runtime Contract
This skill defines how to call the gemini-companion.mjs runtime from Claude Code agents and commands.
Primary entry point
node "${CLAUDE_PLUGIN_ROOT}/scripts/gemini-companion.mjs" task "<prompt and flags>"
Rescue agent rules
- One
Bashcall togemini-companion.mjs task. Return stdout verbatim — no commentary. - Do NOT call
review,challenge,status,result, orcancelfrom consult. - May use
gemini-promptingskill ONLY to shape the prompt before forwarding.
Flag handling
| Flag | Behavior |
|---|---|
--model <alias> |
Passed through to companion; alias resolution happens inside |
--effort <level> |
Reserved for future use (not yet supported by Gemini CLI) |
--resume-last |
Resumes latest Gemini session thread |
--write |
Enables write mode (--yolo inside companion) |
--background / --wait |
Strip these — consult always runs foreground |
--resume / --fresh |
Strip these routing flags; use --resume-last instead |
Default behavior
- Default
--writeunless user explicitly asks for read-only. - Do not add
--background— consult runs synchronously. - Do not interpret or summarize Gemini output — return it verbatim.
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 · 39 lines · 17 tokens per session scan A e95bbec1a100
gemini-cli-runtime is a skill published in the GitHub repository arescope/gemini-plugin-cc (6 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 340 once invoked, about $0.0001 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.
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.