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-claude-setupnpx skills add gabonio/agent-operator-toolkit --skill agent-operator-claude-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-claude-setup)<a href="https://agentmods.dev/skills/gabonio/agent-operator-toolkit/agent-operator-claude-setup"><img src="https://agentmods.dev/badge/skills/gabonio/agent-operator-toolkit/agent-operator-claude-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.00079 | $0.00626 |
| Opus 5 | $0.00039 | $0.00313 |
| Sonnet 5 | $0.00016 | $0.00125 |
| Haiku 4.5 | $0.00008 | $0.00063 |
Grade A, and why
agent-operator-claude-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 4d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Operator Claude Setup
Use Claude Code's native plugin manager. The procedure below is self-contained because installed plugin caches do not include repository-root documentation.
Install
-
Confirm
gitandclaudeare available. -
Add the marketplace inside Claude Code:
/plugin marketplace add gabonio/agent-operator-toolkit -
Install only the requested plugins:
/plugin install agent-operator-setup@agent-operator-toolkit /plugin install builder-kit@agent-operator-toolkit -
Run
/reload-pluginsto activate changes without restarting Claude Code.
Direct installs use user scope by default. To choose user, project, or local scope, use /plugin, open Discover, select the plugin, and choose the scope. Do not select project scope without authorization because it updates repository configuration.
Update
-
Run
/plugin marketplace listand confirm the registered marketplace name. -
Refresh it with
/plugin marketplace update agent-operator-toolkit. -
Update each installed plugin that the user wants to refresh:
/plugin update agent-operator-setup@agent-operator-toolkit /plugin update builder-kit@agent-operator-toolkit -
Run
/reload-plugins. -
If an installed plugin remains unchanged, verify that its published version was bumped.
Third-party marketplace auto-updates are disabled by default. Enable them only when the user requests it through /plugin → Marketplaces → Agent Operator → Enable auto-update.
Diagnose
-
Inspect the Marketplaces, Installed, and Errors tabs under
/plugin. -
Run
/reload-pluginsafter installation, update, enable, or disable operations. -
From this plugin root, run the read-only doctor:
python3 scripts/doctor.py --client claude -
Pass
--marketplace-root <path>when diagnosing a local checkout.
Do not delete ~/.claude/plugins/cache automatically. Cache removal is destructive local recovery and requires explicit user confirmation after native update and reload paths fail.
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.
- 4d ago First seen · 67 lines · 79 tokens per session scan A e0c02d57820f
agent-operator-claude-setup is a skill published in the GitHub repository gabonio/agent-operator-toolkit (1 stars, last pushed 1mo ago), licensed MIT. It adds 79 tokens to every session and 626 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…