cmo-agent-bridge

A plugin that connects an AI agent to Command: Modern Operations, a military strategy game, through a local MCP bridge. It is intended for planning and operating game scenarios written in Lua.

In plain words
What is it for?
Use it to plan or operate live CMO battles, or to build and test CMO scenarios. It is aimed at Lua-based scenario work.
Why use it?
It gives the agent a defined connection for working with the game and its scenarios. Without it, the described game-related bridge and commands are not available to the agent.

Plugin for Claude Code

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.

Claude Code
/plugin marketplace add Nuclear2/cmo-agent-bridge
agentmods
npx agentmods add plugins/nuclear2/cmo-agent-bridge/cmo-agent-bridge
Clone the repo
git clone --depth 1 https://github.com/Nuclear2/cmo-agent-bridge

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

cmo-agent-bridge 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 yesterday.

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/.claude-plugin/plugin.json · 23 lines

What it actually says

{
  "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
  "name": "cmo-agent-bridge",
  "displayName": "CMO Agent Bridge",
  "version": "0.7.3",
  "description": "Plan and operate live CMO battles or build and test CMO scenarios through a local stdio MCP bridge.",
  "author": {
    "name": "Nuclear2",
    "url": "https://github.com/Nuclear2"
  },
  "homepage": "https://github.com/Nuclear2/cmo-agent-bridge#readme",
  "repository": "https://github.com/Nuclear2/cmo-agent-bridge",
  "license": "MIT",
  "keywords": [
    "cmo",
    "command-modern-operations",
    "lua",
    "mcp",
    "wargame"
  ],
  "mcpServers": "./.claude-mcp.json"
}
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.

  1. yesterday First seen · 23 lines scan A fdd19b9eb6ec

Subscribe to this mod's changes

cmo-agent-bridge is a plugin published in the GitHub repository Nuclear2/cmo-agent-bridge (4 stars, last pushed 19d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.