Plugin

superpowers-optimized

Built on the trusted obra/superpowers workflow and refined through research into LLM agent behavior, it adds automatic 3-tier workflow routing, proactive safety hooks, self-consistency verification at critical decision points, cross-session memory, and adversarial red-teaming — everything the original does, plus the discipline layer it was missing. Cross-session memory changes the experience fundamentally. Without it, every session starts blind: the AI re-explores structure it already mapped, re-proposes approaches that were already rejected, re-debugs errors that were already solved. With the four-file memory stack, it arrives knowing what was tried, what was decided, and why — and builds forward instead of sideways. Five research-backed principles run throughout: *less is more* (minimal always-on instructions), *fresh context beats accumulated context* (subagents get clean scoped prompts, not polluted history), *compliance ≠ competence* (instructions must be carefully engineered, not just comprehensive), *verify your own reasoning* (multi-path self-consistency catches confident-but-wrong failures before they become expensive), and *accountability drives accuracy* (agents that know their output has real downstream consequences perform better).

• Published source
• Repository

Analysed

11 October 2026

Last observed

12 October 2026

What the code does

• Runs shell commands Code that starts system commands on the machine it runs on.
• Starts other processes Code that launches separate programs.
• Refers to credential files Code that names files such as SSH keys or cloud credentials.
• Evaluates code at runtime Code that builds and runs code while it executes.
• Runs hooks automatically Hooks that execute without being called explicitly.
• Runs an AI coding agent unsupervised Code that starts an AI coding agent with its approval prompts switched off.
• Reads AI and developer logins Code that refers to AI tool credentials or publishing tokens, such as .npmrc.

Having a capability is not wrongdoing; many tools need these to do their job. It tells you what to check before you install.

This is public metadata, not a safety certification or complete assessment. Static analysis cannot establish what a tool does at runtime.