A pack is an optional harness bundle - skills, slash commands, sub-agents and MCP servers for a focused domain - that you add on demand from the marketplace. Unlike enigma’s built-in policy skills, a pack is never deployed into your normal agent. It runs in a dedicated, isolated agent context, so its skills and commands do not load into - or overload - the agent you use for everyday coding.
Available packs
- Helio - a bug-bounty and offensive-security harness: recon, vulnerability hunting, web2/web3 audit, Active Directory, cloud, triage and report writing. Created in collaboration with the Dymo Intelligence Team.
More packs are on the way. Each one gets its own section here with full documentation.
Why isolation matters
Agents keep every installed skill’s name and description in context at all times (progressive disclosure). Adding a dozen security skills to your normal agent would sit in every session and risk mis-triggering on ordinary coding tasks. A pack avoids that: it is fetched as an asset-only package into a managed directory and deployed only into its own context directory, which the agent reads via its config-dir environment variable. Your normal enigma claude stays clean.
Install and launch
enigma pack <subcommand>
list shows every pack and its install state. install <id> fetches the pack. enigma <id> (e.g. enigma helio) launches an agent in the pack’s isolated context. use <id> <account> pins which login seeds the pack. setup <id> registers the pack’s MCP servers. update/remove keep or delete it.
You can also manage packs from the dashboard’s Packs tab (install, update, remove, pick the seeding account, and copy the launch command).
Which account a pack uses
A pack runs under one of your configured logins, seeded into its isolated context so you do not log in again. You can use any account or profile you have set up - or a brand-new one:
enigma <pack> [account]
enigma <pack> uses the pinned account if you set one, otherwise your active profile’s account (or the tool’s active account). enigma <pack> <account> overrides it for one launch. enigma pack use <pack> <account> pins a per-pack default (- clears it). To use a new login, create it with enigma account add <name> (and log in), then point the pack at it. Target Codex/OpenCode with --tool.
This lets a pack run under a different identity than your everyday agent - for example a dedicated account for authorised security testing - without touching your normal enigma claude setup.
How it works
- Delivery - each pack ships as an asset-only npm package (e.g.
@enigmax/helio) fetched on demand into~/.enigma/packs/<id>, the same on-demand model as the dashboard UI. A workspace checkout is used directly in development. - Isolation - launching a pack deploys its skills, the agent’s command set and its sub-agents into
~/.enigma/packs/<id>/context/<tool>, then spawns the agent pointed at that directory. The context holds only the pack’s content. - Shared login - your chosen account’s credentials are seeded into the context, so the isolated agent is already authenticated.
- MCP and tooling - a pack can ship MCP servers. They are registered only by
enigma pack setup <id>because they need Python and the pack’s tooling, which is heavier than the default skills-and-commands launch.