Plugin community
Risk level
high
65/100

Superpowers 2 ↗

Superpowers 2 is a community-maintained plugin from obra. Anomity scores its risk at 65 out of 100 (high). It matches 1 dangerous capability combination.

filesystem:read filesystem:write shell:execute

Analysis summary

Superpowers 2 is a community-maintained plugin from obra. Anomity scores its risk at 65 out of 100 (high). It matches 1 dangerous capability combination.

The second-generation Superpowers plugin bundles skills together with hooks that enforce a structured test-driven workflow — parallel task execution, code review, and root-cause debugging — rather than leaving the agent to choose whether to follow the process.

Hooks are the meaningful difference from a plain skill library. A hook fires on an event such as a file write or session start, which means part of the plugin runs without the agent deciding to invoke it. That is what makes the workflow stick, and also what makes review important: a hook is code that executes on your machine on a trigger you did not explicitly approve each time. It declares filesystem read and write plus shell execution, inheriting the host agent's authority.

Why this entry scored 65 out of 100

This profile starts at the catalog's neutral base of 50. Because the entry is community-maintained, trust adjusts the score by -10. Declared high-risk capabilities add +20 (capped at +30). It matches 1 dangerous capability combination, which contributes additional severity weight. The clamped result is 65, placing it in the high band.

See the full scoring formula →

Findings

  • Established community project Trust offset
    Contribution to score: -10
  • 2 high-risk capabilities: filesystem:write, shell:execute Critical
    Contribution to score: +20
  • Persistence + execution risk (medium) Medium
    Evidence
    Shell execution plus filesystem write means the agent can plant persistent backdoors (e.g. modifying startup scripts).
    Contribution to score: +5

Capabilities

Every capability the entry declares, with the security implication of each.

  • filesystem:read Filesystem read
    Can read files on the host system. Used for context, indexing, or analysis.
  • filesystem:write Filesystem write
    Can create, edit, or delete files on the host system. High-impact capability — anything from helpful edits to planting persistence.
  • shell:execute Shell execution
    Can run arbitrary shell commands. Combined with network access this becomes effectively a remote shell.

Dangerous combinations matched

Capability pairings that compound into well-known attack patterns.

  • Persistence + execution risk medium
    Shell execution plus filesystem write means the agent can plant persistent backdoors (e.g. modifying startup scripts).
    shell:execute filesystem:write