Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add hekivo/superpowers-sage --skill block-refactoringgit clone --depth 1 https://github.com/hekivo/superpowers-sageWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/hekivo/superpowers-sage/block-refactoring)<a href="https://agentmods.dev/skills/hekivo/superpowers-sage/block-refactoring"><img src="https://agentmods.dev/badge/skills/hekivo/superpowers-sage/block-refactoring/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/hekivo/superpowers-sage/block-refactoring"><img src="https://agentmods.dev/badge/skills/hekivo/superpowers-sage/block-refactoring.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00086 | $0.02135 |
| Opus 5 | $0.00043 | $0.01068 |
| Sonnet 5 | $0.00017 | $0.00427 |
| Haiku 4.5 | $0.00009 | $0.00214 |
Grade A, and why
superpowers-sage:block-refactoring scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Block Refactoring — Evolution of Existing Blocks
Analyze and improve an existing block after its first implementation. Four axes of evolution: design drift detection, CSS coverage analysis, variation expansion, and gap/migration detection.
Announce at start: "I'm using the block-refactoring skill to evolve the block."
When to use
- Block shipped in a previous PR and design has evolved since
- CSS bundle includes rules/tokens that are no longer used
- New design tokens exist in
app.css/design-tokens.mdthat the block could leverage - Legacy block still uses v1 pattern (
.b-{slug}class, dual selector, no custom element) - You suspect implementation diverged from design reference during initial build
When NOT to use
- Creating a new block from scratch → use
/block-scaffoldinginstead - Project-wide convention audit → use
/reviewing - Non-block UI component → Blade components are not ACF blocks
Input
$ARGUMENTS
Resolve to {ClassName} and {slug}. If not provided, ask.
See references/evolution-axes.md for the 4 evolution axes.
Refactoring NEVER rebuilds from scratch. For a full re-scaffold, delegate to /block-scaffolding as a fallback.
Procedure
Phase 0 — Resolve block identity and locate files
From the argument, identify:
{ClassName}— e.g.HeroSection{slug}— e.g.hero-section- 5 target files (one may be absent on legacy blocks):
app/Blocks/{ClassName}.phpresources/views/blocks/{slug}.blade.phpresources/css/blocks/{slug}.cssresources/js/blocks/{slug}.js(may not exist — legacy)resources/css/editor.css(check for@import './blocks/{slug}.css')
Read all present files.
Phase 0b — Shared component inventory
Glob resources/views/components/*.blade.php in the target project (if a path is known, otherwise skip this step).
Build a component inventory table:
| Component slug | File | Likely use |
|---|---|---|
section-header |
section-header.blade.php |
<x-eyebrow> + <h2> pairing |
button |
button.blade.php |
<a> or <button> with utility classes |
card |
card.blade.php |
Repeated card structure |
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 198 lines · 86 tokens per session scan A 92ecd9cb07df
superpowers-sage:block-refactoring is a skill published in the GitHub repository hekivo/superpowers-sage (13 stars, last pushed 3mo ago), licensed MIT. It adds 86 tokens to every session and 2,135 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
menu-transitions-rtl
Animate react-horizontal-scrolling-menu scrolling and build right-to-left menus: noPolyfill defaults to true since v8, so transitionDuration (default 500), a custom-easing-function transitionBehavior, and per-call ScrollOptions { duration, boundary } on scrollToItem/scrollNext/scrollPrev are silently ignored unless…
vite
Vite build tool configuration, plugin API, SSR, and Vite 8 Rolldown migration. Use when working with Vite projects, vite.config.ts, Vite plugins, or building libraries/SSR apps with Vite.