Skip to content

Plugin Development

Plugins are the custom, user-built plays that machines run during a build — install software, create users, drop files, configure services, plant vulnerabilities, deliver attacker tooling. They’re the most-leveraged unit in Rogue Arena: build a plugin once and reuse it across every scenario you ever write.

This section covers how to author your own plugins and how to hand the work to Claude when you’d rather not write YAML by hand.

Most users start by browsing the in-app Plugin Browser — the official Rogue Labs catalog covers a huge surface area (Active Directory roles, common services, vulnerability patterns, attack tooling, monitoring stacks, the lot). Build your own when you want to:

  • Package custom tooling — your favorite C2 framework, a homegrown agent, a niche red-team binary, a custom defender stack — wrap it once in a plugin and drop it on any machine forever
  • Automate installs — turn a 20-step install README into a one-click plugin that runs unattended on every fresh VM
  • Drag-and-drop for the whole team — if you share a plugin with your team workspace, anyone on the team can pull it into their scenario from the in-app Plugin Browser with zero setup
  • Cover gaps in the catalog — when no existing plugin fits your scenario’s specific tool, configuration, or vulnerability pattern
  • Standardize repeatable setups — convert a team checklist into a one-click plugin so everyone gets the same result every time
  • Tune realism — seed specific files, users, scheduled tasks, or registry state that make a lab feel like a real environment

Click a path below to dive in.