A skill for assessing and operating Command: Modern Operations, a military simulation, through the cmo-agent-bridge. It covers scenario actions such as units, sensors, weapons, logistics, missions, and battle assessment.

Use it to inspect live scenarios, plan and execute courses of action, control simulation time, manage contacts and units, configure doctrine and sensors, and assess attacks, losses, and expenditure.

It gives the agent a defined procedure for connecting to the simulation and checking that the bridge and scenario are ready before making changes.

operate-cmo — Skill for Claude Code and Codex by Nuclear2: A skill for assessing and operating Command: Modern Operations…

Install

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.

agentmods

npx agentmods add skills/nuclear2/cmo-agent-bridge/operate-cmo

Any agent

npx skills add Nuclear2/cmo-agent-bridge --skill operate-cmo

Clone the repo

git clone --depth 1 https://github.com/Nuclear2/cmo-agent-bridge

Made for: Claude Code, Codex.

Or install cmo-agent-bridge, the plugin that ships this one along with the rest of its 1 skill, 1 MCP server.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/nuclear2/cmo-agent-bridge/operate-cmo.svg)](https://agentmods.dev/skills/nuclear2/cmo-agent-bridge/operate-cmo)

Your own site

<a href="https://agentmods.dev/skills/nuclear2/cmo-agent-bridge/operate-cmo"><img src="https://agentmods.dev/badge/skills/nuclear2/cmo-agent-bridge/operate-cmo.svg" alt="Measured on agentmods" height="20"></a>

Per session 133 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 7,524 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00133	$0.07524
Opus 5	$0.00067	$0.03762
Sonnet 5	$0.00027	$0.01505
Haiku 4.5	$0.00013	$0.00752

Measured 4d ago against content hash bd4af244b1cb, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

operate-cmo 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.

plugins/cmo-agent-bridge/skills/operate-cmo/SKILL.md · 504 lines

How it starts

The opening of the file, as written. The whole thing — 504 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Operate CMO

Treat MCP results as the authority for the scenario currently open in CMO. Use the MCP tools for normal Agent work and the CLI only for documented setup or fallback paths. Never present an official Lua capability, planned bridge capability, or manually mounted script as an already callable MCP tool.

Establish bridge readiness

At the first CMO interaction in each Agent task, determine whether cmo_bridge_diagnose is present in the registered tool set.

If cmo_bridge_diagnose is present, call it first. If it reports unconfigured or not_prepared, call cmo_bridge_prepare; omit game_root when the reported saved root is the intended installation, otherwise pass a user-confirmed root. The same MCP session becomes ready without a client restart. Then inspect host UI time state. If CMO is running, call cmo_bridge_status without changing speed. If CMO is paused, use one controlled 1x handshake pulse and require final_pause_verified=true before treating pause as restored. A successful status call or handshake pulse establishes the process/runtime/scenario binding required before the first queued mutation.
Before any upgrade or prepare over an existing installation, read the idle-bridge gate in references/setup.md: require queued=0, active=0, and no pending journal. If prepare returns STATE_CONFLICT, do not delete recovery files or switch releases again; use the reported counts with the current/old release to settle the unfinished work first.
If all CMO tools are absent, stop the operational or authoring workflow and read references/setup.md. When a local shell is available, perform the documented uv/uvx checks and pinned release probe yourself. Ask the user only for missing permission, an ambiguous CMO installation path, or CMO editor work.
Do not run cmo-bridge serve as a detached or interactive terminal process. The Agent client owns that stdio process, and a manually started server cannot add tools to the current task.
After repairing a missing-tool startup failure, have the user fully restart the Agent client and open a new task. This restart is needed only when the tools themselves were absent; MCP-side cmo_bridge_prepare hot-activates an already registered tool set.
If cmo_bridge_diagnose reports ready, inspect host UI time state before the first CMO-backed call. Use cmo_bridge_status while running or the handshake-pulse path while paused. If either path fails, recover the polling event as described in the setup reference.

Read the full file on GitHub · 504 lines

Files

What ships with it

8 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.

Changes

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 · 504 lines · 133 tokens per session scan A bd4af244b1cb

Subscribe to this mod's changes

operate-cmo is a skill published in the GitHub repository Nuclear2/cmo-agent-bridge (5 stars, last pushed 21d ago), licensed MIT. It adds 133 tokens to every session and 7,524 once invoked, about $0.0007 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.

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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.

obra/superpowers · 37 tokens

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.

microsoft/vscode · 62 tokens

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.

microsoft/vscode · 51 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens