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/gabonio/agent-operator-toolkit/agent-operator-gemini-setupnpx skills add gabonio/agent-operator-toolkit --skill agent-operator-gemini-setupgit clone --depth 1 https://github.com/gabonio/agent-operator-toolkitWrote 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/skills/gabonio/agent-operator-toolkit/agent-operator-gemini-setup)<a href="https://agentmods.dev/skills/gabonio/agent-operator-toolkit/agent-operator-gemini-setup"><img src="https://agentmods.dev/badge/skills/gabonio/agent-operator-toolkit/agent-operator-gemini-setup.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 | $0.00073 | $0.00493 |
| Opus 5 | $0.00036 | $0.00246 |
| Sonnet 5 | $0.00015 | $0.00099 |
| Haiku 4.5 | $0.00007 | $0.00049 |
Grade A, and why
agent-operator-gemini-setup 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 3d 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
Agent Operator Gemini Setup
Gemini CLI installs Agent Operator as one extension containing the marketplace's portable skills and commands.
Install
Run from a terminal, outside the Gemini interactive session:
gemini extensions install https://github.com/gabonio/agent-operator-toolkit
Add --auto-update only when the user requests automatic updates. For local development, use gemini extensions link <checkout-path> instead of copying files into ~/.gemini manually.
Restart Gemini CLI after installation. Inside Gemini, verify the extension and reload its components:
/extensions list
/skills reload
/commands reload
The setup command is /agent-operator:setup.
Update
Run from a terminal:
gemini extensions update agent-operator-toolkit
Then restart Gemini CLI. Extension management changes take effect after restart.
Diagnose
-
Run
gemini extensions listin a terminal or/extensions listinteractively. -
Confirm the extension is enabled and its version/source are expected.
-
Run the read-only doctor from this checkout or extension root:
python3 plugins/agent-operator-setup/scripts/doctor.py --client gemini --marketplace-root . -
Use
/skills list,/commands list,/skills reload, and/commands reloadto inspect discovery.
Remove or disable
Use native commands:
gemini extensions disable agent-operator-toolkit --scope user
gemini extensions enable agent-operator-toolkit --scope user
gemini extensions uninstall agent-operator-toolkit
Boundaries
- Installing or linking an extension changes user-level state and requires user intent.
- Do not pass
--consent, enable auto-update, or choose a workspace scope unless requested. - Preserve unrelated Gemini extensions, settings, skills, commands, hooks, agents, and MCP servers.
- Ask before deleting
~/.gemini/extensionscontent or replacing extension metadata.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 68 lines · 73 tokens per session scan A bd4710a1d559
agent-operator-gemini-setup is a skill published in the GitHub repository gabonio/agent-operator-toolkit (1 stars, last pushed 1mo ago), licensed MIT. It adds 73 tokens to every session and 493 once invoked, about $0.0004 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…