Superpowers Hit 250K Stars, Then Developers Started Ripping It Out
Agent scaffolding that burns context and slows iteration is now a net negative for capable models like Fable 5. Teams still running heavy skill suites are paying token costs for process guardrails the model already internalized, and the right default is shifting from 'install everything' to 'enable nothing, add only what breaks without it.'
Superpowers, a Claude Code plugin with over 250,000 GitHub stars, forces every task through a rigid six-step workflow of brainstorming, spec-writing, planning, TDD, coding, and review. What once solved a real problem—reckless agents that coded without thinking—has become a liability. Users report that trivial fixes like renaming a variable balloon from ten seconds to five minutes, while startup alone burns 22,000 tokens before any work begins.
The backlash isn't just about speed. Forcing 14 skill modules into a limited context window divides the model's attention, and some developers find Claude makes more mistakes with Superpowers installed than without. A competing project, fable-skills, takes the opposite approach with only six lightweight nudges at key decision points, and stress testing with Opus 4.8 suggests that's all a modern agent needs.
The underlying shift is model capability. Fable 5 investigates dependencies, plans approaches, and verifies its own output without external prompting. The pattern mirrors early smartphone app ecosystems: flashlight and calculator apps vanished once the OS absorbed those functions. Skill plugins that once compensated for weak reasoning are now redundant overhead, and the correct posture for late 2026 is a well-written CLAUDE.md plus one or two on-demand skills for specific scenarios.
Skill plugins follow the same lifecycle as early smartphone apps: they compensate for missing platform capability, then become dead weight once the platform absorbs those functions.
The token economics of heavy process scaffolding flip from helpful to harmful at a specific model-capability threshold, and Fable 5 appears to have crossed it.
Developer intuition about 'more process equals better output' breaks down when the process itself consumes the context window the model needs to reason well.
Uninstalling a 250k-star tool isn't a rejection of its design; it's a signal that the layer it occupied no longer exists.
The discussion splits between those who still find the skill useful and those who see its obsolescence as inevitable. One side argues that simple edits don't warrant the token overhead of a heavy plugin, while the other maintains the skill still has a place for complex reasoning tasks. A broader view holds that model-native capabilities will absorb these tools entirely, making project-level configuration the only lasting need.
So aligned with my thinking. Skills like this only need to be set at the project level. Going forward, even various open-source libraries for saving tokens will gradually disappear. This is something the large model companies themselves should be doing. Artificial intelligence isn't artificial stupidity; it should let anyone simply and directly use the fastest and cheapest AI.
I installed it, and I enable it for complex thinking and sorting tasks. I agree with what you said. Many agents are converging these useful skills into native capabilities. Maybe after a while, I'll consider uninstalling it.