Skip to content
Arena Docs

Agent MCP for Plugin Development

With the Rogue Arena MCP plugin loaded, your agent runs the full plugin development loop. It researches offline install paths, scaffolds the project, writes the YAML, manages vault files, and iterates until the plugin is ready to ship. Two skills do the work, one after the other.

/rogue-plugin-brainstorm

Section titled “/rogue-plugin-brainstorm”

Research the install path, then scaffold every local file develop needs.

What it does:

  • Researches exhaustively online: install paths, version pins, dependency trees, and offline-friendly options.
  • Plans the plugin slate: one plugin or a coordinated set, with names, descriptions, and parent/child relationships.
  • Prompts you for empty plugin IDs (or an empty canvas) so it has a place to put the YAML and vault files.
  • Scaffolds every project locally: YAML files, download scripts, vault folders, and project.json metadata.
  • Hands the bundle off to /rogue-plugin-develop, which turns the drafts into working plugins.

It runs the same research for any target:

  • “Three RCE-vulnerable Linux apps” → finds candidates, picks specific versions with documented CVEs, and weighs ease of install against realism.
  • “Outlook on Windows with mailbox content” → finds the right Office install path, picks an offline-installable channel, plans the mailbox seeding, and lines up the Auto-Login dependencies.
  • “Elastic Stack server + Agent on every endpoint” → splits the work across several plugins, plans the parent/child wiring, and flags which boxes need internet during the build.

/rogue-plugin-develop

Section titled “/rogue-plugin-develop”

Iterate on the scaffolded YAML until it’s a working plugin.

What it does:

  • Reads the local files brainstorm produced (or starts from an existing plugin you point it at).
  • Builds out the testing canvas: VLANs, machines, a DC if needed, and the right plugins with every param filled in.
  • Reads deploy logs after you click Commit & Apply, and triages failures end to end.
  • Loops: write YAML → build → read log → fix → repeat until the plugin installs cleanly with no internet at deploy time.
  • Pushes the final YAML, params, and vault files to the platform through MCP.