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 architectinggit 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/architecting)<a href="https://agentmods.dev/skills/hekivo/superpowers-sage/architecting"><img src="https://agentmods.dev/badge/skills/hekivo/superpowers-sage/architecting/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/architecting"><img src="https://agentmods.dev/badge/skills/hekivo/superpowers-sage/architecting.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.00051 | $0.00645 |
| Opus 5 | $0.00026 | $0.00322 |
| Sonnet 5 | $0.00010 | $0.00129 |
| Haiku 4.5 | $0.00005 | $0.00064 |
Grade A, and why
superpowers-sage:architecting 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecting (Compatibility Mode)
This skill remains available to avoid breaking existing workflows. It now orchestrates the new split flow:
superpowers-sage:architecture-discoverysuperpowers-sage:plan-generator
Announce at start: "I'm using architecting compatibility mode and will run architecture-discovery then plan-generator."
Input
$ARGUMENTS
HARD GATE
Do not implement code in this skill. If implementation is requested, complete the split planning flow first.
Procedure
0) Design system gate
Before starting architecture discovery, check whether the visual foundation exists:
- Does
resources/css/design-tokens.cssexist and contain real tokens (not a placeholder)? - Does a kitchensink route/view exist (e.g.,
resources/views/kitchensink.blade.phpor/kitchensinkis accessible)?
If both are present: proceed to Step 1 normally.
If either is missing or unvalidated:
⚠ Design system foundation not found.
Architecture for multi-block features should follow a validated design system.
Tokens, UI atoms, and layout components must exist before defining block schemas.
Recommendation: run /sage-design-system first.
→ It will create design-tokens.css, ui/ + layout/ Blade components, and validate with a kitchensink page.
→ Return to /architecting after the kitchensink screenshot is confirmed.
Proceed anyway? (only if this feature has no visual blocks / is purely backend)
Wait for explicit user confirmation before skipping the design system gate.
1) Run architecture discovery
- Invoke
superpowers-sage:architecture-discoverywith the same arguments. - Wait for explicit user approval of the written architecture spec.
2) Run plan generation
- Invoke
superpowers-sage:plan-generatorwith the approved spec path. - Ensure output plan includes strategy, dependencies, and per-component execution ordering.
3) Transition to execution
After plan generation, offer:
subagent-driven-developmentfor parallel task execution in this sessionsuperpowers-sage:buildingfor direct implementation from plan files
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 · 84 lines · 51 tokens per session scan A 4d575b95c011
superpowers-sage:architecting is a skill published in the GitHub repository hekivo/superpowers-sage (13 stars, last pushed 3mo ago), licensed MIT. It adds 51 tokens to every session and 645 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…