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 skills add asfbay-bit/opchain-skills --skill oc-fleet-opsgit clone --depth 1 https://github.com/asfbay-bit/opchain-skillsWrote 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/asfbay-bit/opchain-skills/oc-fleet-ops)<a href="https://agentmods.dev/skills/asfbay-bit/opchain-skills/oc-fleet-ops"><img src="https://agentmods.dev/badge/skills/asfbay-bit/opchain-skills/oc-fleet-ops/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/asfbay-bit/opchain-skills/oc-fleet-ops"><img src="https://agentmods.dev/badge/skills/asfbay-bit/opchain-skills/oc-fleet-ops.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00200 | $0.04842 |
| Opus 5 | $0.00100 | $0.02421 |
| Sonnet 5 | $0.00040 | $0.00968 |
| Haiku 4.5 | $0.00020 | $0.00484 |
Grade A, and why
oc-fleet-ops 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 8d 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 — 400 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fleet Ops
On first invocation, read references/orchestrator.md and follow its welcome protocol.
Deploy and operate one-or-more containers across arbitrary, self-managed environments
— the territory oc-deploy-ops routes elsewhere today. Where deploy-ops is opinionated
about a single app on a managed PaaS (Workers, Render, Fly, Shuttle), Fleet Ops owns
the messier other half: multi-container orchestration (k8s/Nomad/Compose/Swarm),
infrastructure-as-code (Terraform and its alternatives), and arbitrary environments
(on-prem Linux VMs, GCE, bare metal). It is also the skill that lands the modules
oc-modularize-ops carves out of a former monolith — once the seams are proven, the
fleet is where those modules actually run.
This is not a tri-agent forge and not a managed-PaaS deployer. It is a gated ops operator: declare what runs where, provision the infra with the IaC tool that fits (not Terraform by reflex), roll the fleet behind a strategy, verify health across every replica and cross-service edge, then operate day-2 — scale, drain, replace, roll back. The IaC apply step is the highest-blast-radius operation in the entire opchain catalog, so it is gated behind a mandatory dry-run/plan that never auto-applies.
Mnemonic: deploy-ops pushes one app to a platform; fleet-ops stands up and runs a fleet on infra you own. deploy-ops ↔ fleet-ops are peers, not a chain — the orchestrator routes by "managed app vs self-managed fleet" (see Boundaries). When a project carries both checkpoints, that's the disambiguator.
/oc-fleet — Command Reference
FLEET OPS COMMANDS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
PLAN & PROVISION
/oc-fleet Show fleet status for the current project (this menu if none)
/oc-fleet topology Declare containers/services × target environment(s)
/oc-fleet provision Stand up infra with the right IaC tool (gated dry-run first)
DEPLOY & VERIFY
/oc-fleet deploy Roll the fleet with a rollout strategy (rolling/blue-green/canary)
/oc-fleet verify Fleet-wide health: every replica, every cross-service edge
DAY-2 OPERATE
/oc-fleet scale Scale replicas/nodes to a target (applies; never decides)
/oc-fleet drain Cordon + drain a node for maintenance / replace a container
/oc-fleet rollback Roll the whole fleet back to last-good
UTILITIES
/oc-fleet status Current topology, fleet_health, last deploy, rollback availability
/checkpoint Show checkpoint status
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Type any command to begin. /oc-fleet to see this again.
What ships with it
2 files 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.
- 8d ago Changed e6dc8d342621
- 11d ago First seen · 400 lines · 200 tokens per session scan A d591e1de68be
oc-fleet-ops is a skill published in the GitHub repository asfbay-bit/opchain-skills (0 stars, last pushed 7d ago), licensed Apache-2.0. It adds 200 tokens to every session and 4,842 once invoked, about $0.0010 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
azd-deployment
Deploy containerized frontend + backend applications to Azure Container Apps with remote builds, managed identity, and idempotent infrastructure.
openshell-cli
Guide agents through using the OpenShell CLI (openshell) for sandbox management, gateway registration, provider configuration and refresh, policy iteration, settings, service exposure, BYOC workflows, and attached-provider inference. Covers basic through advanced multi-step workflows. Trigger keywords - openshell…
langbot-deploy
Deploy and configure a LangBot instance — Docker / Docker Compose, Kubernetes, the config.yaml model, the Box sandbox runtime, the plugin runtime, and the global API key. Use when installing, deploying, upgrading, or configuring LangBot in production or self-hosted environments. Triggers on "deploy langbot", "langbot…
compute-env-setup
Set up a compute environment on a remote provider so Claude Science jobs can run there. Covers direct SSH/conda hosts, Slurm clusters, container-via-bridge runners, and managed-API providers (Modal, GCP, RunPod). Use when standing up a new provider, porting an env to a different backend, adding a tool that needs its…
azure-cloud-migrate
Assess and migrate cross-cloud workloads to Azure with reports and code conversion. Supports Lambda→Functions, Beanstalk/Heroku/App Engine→App Service, Fargate/Kubernetes/Cloud Run/Spring Boot→Container Apps. WHEN: migrate Lambda to Functions, AWS to Azure, migrate Beanstalk, migrate Heroku, migrate App Engine, Cloud…
atmos-helmfile
Helmfile orchestration: sync/apply/destroy/diff, Kubernetes deployments, varfile generation, EKS integration, source management.