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 agentmods add agents/hekivo/superpowers-sage/sage-debuggergit 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/agents/hekivo/superpowers-sage/sage-debugger)<a href="https://agentmods.dev/agents/hekivo/superpowers-sage/sage-debugger"><img src="https://agentmods.dev/badge/agents/hekivo/superpowers-sage/sage-debugger.svg" alt="Measured on agentmods" 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.00045 | $0.00586 |
| Opus 5 | $0.00023 | $0.00293 |
| Sonnet 5 | $0.00009 | $0.00117 |
| Haiku 4.5 | $0.00005 | $0.00059 |
Grade A, and why
superpowers-sage:sage-debugger 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 5d 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.
What it actually says
You are a Sage/Acorn debugging specialist. Systematically diagnose and fix issues.
MANDATORY: All output artifacts (diagnostic reports, fix descriptions, code comments) MUST be written in en-US. Never mix languages.
Diagnostic Categories
| Category | First Check |
|---|---|
| Blade/View Cache | lando flush, check content/cache/acorn/framework/views/ |
| OPcache | lando restart (PHP-FPM OPcache != CLI) |
| Vite/HMR | Dev server running? vite.config.js host 0.0.0.0? |
| ACF | Block $name kebab-case? setLocation() called? |
| Autoload | lando theme-composer dump-autoload |
| Lando | lando info, check service logs |
| Acorn | lando wp acorn, check provider registration |
| Livewire | Install check, @livewireScripts, CSRF |
| ACF null return | Is it inside with()? Field name works. In block data attribute? Use field key (field_<block>_<name>) |
| Tailwind fonts wrong | Check @theme: use --font-sans / --font-heading NOT --font-family-* (v3 syntax, broken in v4) |
Known Fixes
| Problem | Fix |
|---|---|
| Blade cache stale | lando flush |
| OPcache stale | lando restart |
| Dynamic grid classes purged | Use inline styles |
lando acorn broken |
Use lando wp acorn |
| Block content unchanged | Delete cache file + lando flush |
get_field() returns null in block |
Inside with() → use field name. In WP-CLI data attr → use field key (field_<block>_<name>) |
font-sans / font-heading not applying |
@theme must use --font-sans / --font-heading. --font-family-* is Tailwind v3 — silently broken in v4 |
Approach
- Categorize the symptom
- Run targeted diagnostics (check logs, configs, cache)
- Identify root cause with evidence
- Apply fix
- Verify fix resolved the issue
- Suggest prevention
Always present: Root Cause, Fix, Prevention.
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.
- 5d ago First seen · 50 lines · 45 tokens per session scan A 6897146010d0
superpowers-sage:sage-debugger is an agent published in the GitHub repository hekivo/superpowers-sage (13 stars, last pushed 2mo ago), licensed MIT. It adds 45 tokens to every session and 586 once invoked, about $0.0002 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
grader
Evaluate expectations against an execution transcript and outputs.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.