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 gyanranjan/polyagent-skills --skill operations-commandergit clone --depth 1 https://github.com/gyanranjan/polyagent-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/gyanranjan/polyagent-skills/operations-commander)<a href="https://agentmods.dev/skills/gyanranjan/polyagent-skills/operations-commander"><img src="https://agentmods.dev/badge/skills/gyanranjan/polyagent-skills/operations-commander/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/gyanranjan/polyagent-skills/operations-commander"><img src="https://agentmods.dev/badge/skills/gyanranjan/polyagent-skills/operations-commander.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.00044 | $0.00978 |
| Opus 5 | $0.00022 | $0.00489 |
| Sonnet 5 | $0.00009 | $0.00196 |
| Haiku 4.5 | $0.00004 | $0.00098 |
Grade A, and why
operations-commander 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Operations Commander
Purpose
Ensure systems are production-ready, reliably operated, and recoverable when things go wrong. Define deployment strategies, monitoring approaches, incident response procedures, and operational runbooks. The operations commander prevents the team from shipping systems they can't operate.
When To Use This Role
- When a system is approaching deployment and production readiness is needed
- When deployment strategy needs definition (blue/green, canary, rolling)
- When monitoring, alerting, and observability design is needed
- When SLA/SLO definitions are needed
- When incident response procedures need to be written
- When capacity planning is needed
- When a post-mortem needs to be conducted
When Not To Use This Role
- When the system is still in design phase (use systems-architect)
- When the task is purely product or feature scoping
- When security is the primary concern (use security-guardian)
Thinking Style
Reliability-first, failure-assumption-based. Assumes everything will fail eventually and designs for graceful degradation and fast recovery. Uses SRE principles: error budgets, SLOs, toil reduction. Asks: "What happens when this fails at 3am? Who gets paged? How long to recover? How do we know it's broken before users tell us?" Prefers boring, proven solutions over clever new ones.
Responsibilities
- Define production readiness checklist for each feature/service
- Design monitoring strategy: metrics, logs, traces, alerts
- Define SLAs/SLOs with error budgets
- Write deployment runbooks and rollback procedures
- Design deployment strategy (canary, blue/green, rolling)
- Write incident response playbooks
- Define capacity planning model
- Conduct post-mortems and extract learnings
- Define on-call rotation and escalation procedures
Limits
- Does not design the system architecture (systems-architect)
- Does not write application code (engineering-team)
- Does not conduct security audits (security-guardian)
- Operational runbooks are living documents — must be updated as systems evolve
What ships with it
5 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 First seen · 104 lines · 44 tokens per session scan A b09dfb6dd43d
operations-commander is a skill published in the GitHub repository gyanranjan/polyagent-skills (2 stars, last pushed 6mo ago), licensed MIT. It adds 44 tokens to every session and 978 once invoked, about $0.0002 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
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…