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 skills/hekivo/superpowers-sage/debuggingnpx skills add hekivo/superpowers-sage --skill debugginggit 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/debugging)<a href="https://agentmods.dev/skills/hekivo/superpowers-sage/debugging"><img src="https://agentmods.dev/badge/skills/hekivo/superpowers-sage/debugging.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 | $0.00135 | $0.01188 |
| Opus 5 | $0.00068 | $0.00594 |
| Sonnet 5 | $0.00027 | $0.00238 |
| Haiku 4.5 | $0.00014 | $0.00119 |
Grade A, and why
superpowers-sage:debugging 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 3d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debugging — Sage-Aware Troubleshooting
Diagnose and fix issues in Sage/Acorn/Lando projects with domain-specific knowledge of common pitfalls.
Base skill: This wraps systematic-debugging with Sage domain knowledge.
Inputs
$ARGUMENTS
Procedure
0) Categorize the issue
| Category | Symptoms | First Check |
|---|---|---|
| Blade/View Cache | Template not updating, old content showing | lando flush |
| OPcache | PHP changes not reflected despite cache clear | lando restart |
| Vite/HMR | Styles missing, HMR not connecting | Check dev server, vite.config.js |
| ACF Registration | Block not appearing, fields missing | ACF sync, block class $name |
| Lando Services | Container errors, service unavailable | lando info, service logs |
| Acorn Boot | Command not found, provider failure | lando wp acorn, config cache |
| Livewire | Component not rendering, wire actions failing | Install check, CSRF, Alpine |
| Tailwind Purge | Classes not applying in production | @source paths, CSS-first config |
| Database | Connection refused, migration errors | .env DB config, Lando service |
| Autoload | Class not found | lando theme-composer dump-autoload |
1) Run targeted diagnostics
Based on category, investigate:
Blade/View Cache
lando flush # Clear all caches
ls content/cache/acorn/framework/views/ # Check for stale compiled views
- If
lando flushdoesn't help, check for stale files directly - PHP-FPM OPcache is separate from CLI OPcache —
lando restartfor FPM
Vite/HMR
lando vite # Start dev server
- Check
vite.config.js:server.hostmust be'0.0.0.0' - Check
.lando.ymlproxy includes Vite port - Check
@vite()directive in layout blade
ACF Registration
lando acorn acf:sync # Sync field groups
- Block
$namemust be kebab-case fields()must callsetLocation()with()must return array
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.
- 3d ago First seen · 125 lines · 135 tokens per session scan A a5f5e08091c3
superpowers-sage:debugging is a skill published in the GitHub repository hekivo/superpowers-sage (13 stars, last pushed 2mo ago), licensed MIT. It adds 135 tokens to every session and 1,188 once invoked, about $0.0007 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
wxjava-module-selector
根据微信公众号、小程序、微信支付、企业微信、开放平台、视频号或微信小店、腾讯企点和微信智能对话等业务场景，为用户选择合适的 WxJava Maven 模块、BOM 和示例入口。适用于用户询问“该用哪个模块”、依赖坐标、产品边界或单/多账号 Starter 选择时。.
cpp-pro
Writes, optimizes, and debugs C++ applications using modern C++20/23 features, template metaprogramming, and high-performance systems techniques. Use when building or refactoring C++ code requiring concepts, ranges, coroutines, SIMD optimization, or careful memory management — or when addressing performance…
rust-pro
Master modern Rust (2024 edition) with async patterns, advanced type system features, and production-ready systems programming. Expert in the current Rust ecosystem including Tokio, axum, and modern crates. Use PROACTIVELY for Rust development, performance optimization, or systems programming.
ax-python-agent
Use when writing Python code with axllm for agents, child delegation, tools, MCP, citations, persistent playbook learning, stage instructions, runtime state, final typed responses, and direct-respond executor skipping.
mps-aspect-actions
Use when defining or editing MPS node factories (the "actions" aspect) — NodeFactories roots, per-concept NodeFactory setup functions that initialize a freshly created node and optionally copy data from a replaced sampleNode, plus the actions aspect's CopyPasteHandlers and PasteWrappers roots. Reach for this skill…
typescript-functions
Apply, review, and explain TypeScript function conventions. Use automatically for tasks involving function responsibility, statelessness, purity, side effects, function arguments, function API design, or return types.