Superpowers 6: What Actually Changed, and Why Your Agent Got Harder to Fool

Mon, 13 Jul 2026 15:30:00 +0800

The short answer

If you already write code with Claude Code, OpenCode, or Codex, you have probably heard of Superpowers. It is not another “magic prompt.” It is a skill framework that makes your agent work by process — turning the habits of a good engineer (“think before you act”, “write the test before the code”, “collect evidence before fixing the bug”) into operating procedures the agent must follow.

From v6.0.0 to the latest v6.1.1, Superpowers shipped a dense run of upgrades: Subagent-Driven Development (SDD) lost half its reviewers but got stricter; plans gained a Global Constraints block and per-task Interfaces; the brainstorming companion got a one-time key; Codex can install from the marketplace; and Gemini CLI was dropped after Google EOLed it.

This article unpacks the wave, what you actually get, and why it makes your agent’s output steadier.

Small Models Make Agents Drift. Superpowers Gives Them Rails.

Thu, 07 May 2026 16:43:10 +0800

The short version

When an agent powered by a smaller or weaker model behaves unpredictably, the problem is not always solved by writing a longer prompt. Smaller models often struggle with long-horizon consistency, tool discipline, evidence tracking, and multi-step execution. Superpowers does not turn a weak model into a frontier model. What it does is more practical: it gives the agent an external engineering workflow made of reusable Skills, checkpoints, testing habits, debugging rules, review steps, and completion verification.

For agents such as OpenClaw, HermesAgent, Codex, Claude, Gemini, OpenCode, Droid, Cursor, and similar tools, Superpowers is best understood as an engineering-discipline layer. It makes the agent less dependent on improvisation and more likely to follow a repeatable process.

This article is about a very common failure mode in modern agent workflows: the model can talk fluently, but the agent does not behave reliably once the task becomes long, stateful, tool-heavy, or distributed across multiple agents.

The issue becomes more visible when using smaller domestic models, local models, quantized models, or cost-optimized models. They may answer normal questions well enough, but once they need to read a repository, follow a constraint, modify files, run tests, interpret logs, preserve privacy, and report only verified results, the instability becomes obvious.

All examples in this article are generic. No private hostnames, internal addresses, credentials, project names, or personal paths are included.

Superpowers on Margrop Blog

Superpowers 6: What Actually Changed, and Why Your Agent Got Harder to Fool

Small Models Make Agents Drift. Superpowers Gives Them Rails.