
Agent Operators
Install a suite of guarded CLI operator subagents so Claude Code runs git, GitHub, Bun, and Cloudflare Wrangler commands through enforced hooks instead of ad-hoc shell chaos.
Overview
agent-operators is a plugin marketplace for the Build phase that packages six operator subagent plugins with CLI enforcement hooks for git, GitHub, Bun, and Cloudflare Wrangler.
What is this marketplace?
- Six plugins: operator-system base plus GitHub, Bun, and Cloudflare Wrangler operators (and related scaffolds).
- operator-system provides CLI enforcement hooks, subagent lifecycle tracking, git-operator, and scaffolding for new opera
- operator-github guards gh for PRs, issues, Actions, and releases.
- operator-bun guards bun and bunx for runtime, packages, and testing.
- operator-cloudflare-wrangler covers Workers, KV, R2, and queues via Wrangler.
- 6 plugins in the marketplace
- operator-system covers git enforcement, hooks, and operator scaffolding
- Dedicated operators for GitHub gh, Bun/bunx, and Cloudflare Wrangler
Community signal: 1 GitHub stars.
What problem does it solve?
Solo builders let agents run gh, bun, and wrangler blindly and lose auditability when commands diverge from project conventions.
Who is it for?
Claude Code users who want subagent specialization and hook-based CLI guardrails across git, GitHub, Bun, and Cloudflare.
Skip if: Teams that only need a single MCP server or do not use Claude Code plugin marketplaces.
What do I get? / Deliverables
After registering the marketplace, Claude can invoke scoped operator subagents with guarded CLIs and a repeatable pattern for adding new operators.
- Six registerable operator plugins with documented keywords and sources
- Reusable operator-system hooks and scaffolding for additional operators
Plugins in this marketplace
6 plugins — install individually after you add the marketplace.
Recommended Marketplaces
Journey fit
Operator plugins are where solo builders wire agent behavior to real dev tooling—canonical shelf is Build because you add them while assembling your agent stack. Subagents, lifecycle hooks, and scaffolding for new operators are core agent-tooling infrastructure, not a one-off integration script.
How it compares
Operator subagent marketplace with enforcement hooks, not a standalone skill or raw MCP listing.
Common Questions / FAQ
Who is Agent Operators for?
It is for Claude Code builders who delegate repo, package-manager, and edge-deploy commands to named operator subagents instead of unconstrained terminal use.
When should I use Agent Operators?
Use it when you are stabilizing an agent dev workflow across git, GitHub, Bun, or Wrangler and want shared scaffolding plus per-tool operators.
How do I add Agent Operators to my agent?
Add the htxryan/Agent Operators Claude marketplace from the publisher repo, then enable the operator-system and tool-specific plugins your stack needs.