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/arcobaleno64/agy-plugin-cc/gemini-cli-runtimenpx skills add arcobaleno64/agy-plugin-cc --skill gemini-cli-runtimegit clone --depth 1 https://github.com/arcobaleno64/agy-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.00019 | $0.00929 |
| Opus 5 | $0.00010 | $0.00464 |
| Sonnet 5 | $0.00004 | $0.00186 |
| Haiku 4.5 | $0.00002 | $0.00093 |
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 yesterday.
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 Runtime
Use this skill only inside the gemini:gemini-rescue subagent.
Primary helper:
node "${CLAUDE_PLUGIN_ROOT}/scripts/gemini-companion.mjs" task "<raw arguments>"
Execution rules:
- The rescue subagent is a forwarder, not an orchestrator. Its only job is to invoke
taskonce and return that stdout unchanged. - Prefer the helper over hand-rolled CLI strings, git operations, or any other Bash activity.
- Do not call
adversarial-review,status,result, orcancelfromgemini:gemini-rescue. - Use
taskfor every rescue request, including diagnosis, planning, research, and explicit fix requests. - You may use the
gemini-promptingskill to rewrite the user's request into a tighter prompt before the singletaskcall. - That prompt drafting is the only Claude-side work allowed. Do not inspect the repo, solve the task yourself, or add independent analysis outside the forwarded prompt text.
- Leave
--effortunset unless the user explicitly requests a specific effort. - Leave model unset by default. Add
--modelonly when the user explicitly asks for one. - Model aliases (source of truth:
MODEL_ALIAS_ENTRIESinplugins/gemini/scripts/lib/model-map.mjs):flash/flash3→gemini-3-flash-preview,pro/pro3→gemini-3.1-pro-preview,lite3→gemini-3.1-flash-lite,flash25→gemini-2.5-flash,pro25→gemini-2.5-pro,lite/fast→gemini-2.5-flash-lite. - Read-only is the default; add
--writeonly when the user explicitly asked for edits.
Command selection:
- Use exactly one
taskinvocation per rescue handoff. - If the forwarded request includes
--backgroundor--wait, treat that as Claude-side execution control only. Strip it before callingtask. - If the forwarded request includes
--model, normalize aliases and pass it through. - If the forwarded request includes
--effort, pass it through totask. - If the forwarded request includes
--timeout <seconds>, pass it through totask. Whole seconds, 30 to 3600. It bounds both the run's duration and the amount of output it can emit before being killed. --effortaccepted values: Gemini engine acceptsnone,minimal,low,medium,high,xhigh; AGY engine accepts onlylow,medium,high.--resume: add--resume-last, even if the request text is ambiguous.--fresh: use a freshtaskrun, do not add--resume-last.task --resume-last: for "keep going", "resume", "apply the top fix", or "dig deeper".
Engine routing:
- Gemini CLI and AGY are both first-class supported engines; only the selected engine's CLI is required.
- Default engine: credential-gated auto-detection (selects Gemini if installed and authenticated with valid credentials, otherwise AGY).
- Force AGY: add
--engine agy. - Force Gemini CLI: add
--engine gemini. - Note for AGY engine:
--modeltakes an exact model ID fromagy modelsor--effortacceptslow,medium, orhigh; the two cannot be combined, and Gemini model aliases are rejected for AGY.
Safety rules:
- Read-only is the default in
gemini:gemini-rescue; add--writeonly when the user explicitly asked for edits. - Preserve the user's task text as-is apart from stripping routing flags.
- Do not inspect the repository, read files, grep, monitor progress, poll status, fetch results, cancel jobs, summarize output, or do any follow-up work of your own.
- Return the stdout of the
taskcommand exactly as-is. - If the Bash call fails or the engine cannot be invoked, return nothing.
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.
- yesterday First seen · 52 lines · 19 tokens per session scan A f21f77f520e5
gemini-cli-runtime is a skill published in the GitHub repository arcobaleno64/agy-plugin-cc (10 stars, last pushed yesterday), licensed MIT. It adds 19 tokens to every session and 929 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
conductor-setup
Scaffolds the project and sets up the Conductor environment. Use this whenever a project needs to be initialized or if the Conductor configuration is missing.
conductor-new-track
Plans a new track (feature or bug fix), generates spec/plan documents, and updates the registry.
conductor-review
Reviews the completed track work against guidelines and the plan. Acts as a Principal Software Engineer to ensure quality and compliance.
mantis-calibrate
Calculates the final risk score based on empirical evidence and architectural impact. Use when findings have been fully processed by previous stages and you need to append final risk scores to the finding files. Don't use for discovering new vulnerabilities or writing patches.
mantis-reproduce
Generates and runs crash reproducers to verify security flaws. Use when viable findings exist and you need to write and execute a script or payload to verify the crash. Don't use for code auditing or patching.
mantis-structural-index
Builds a content-addressed semantic-unit index from source code for structural context. Use when a pinned or live codebase is available and structural cross-reference data would improve research quality. Don't use for findings analysis, patching, or reporting.