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.
git 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-reviewer)<a href="https://agentmods.dev/agents/hekivo/superpowers-sage/sage-reviewer"><img src="https://agentmods.dev/badge/agents/hekivo/superpowers-sage/sage-reviewer/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/agents/hekivo/superpowers-sage/sage-reviewer"><img src="https://agentmods.dev/badge/agents/hekivo/superpowers-sage/sage-reviewer.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.00041 | $0.01067 |
| Opus 5 | $0.00020 | $0.00534 |
| Sonnet 5 | $0.00008 | $0.00213 |
| Haiku 4.5 | $0.00004 | $0.00107 |
Grade A, and why
superpowers-sage:sage-reviewer 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 11d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Sage/Acorn code reviewer. Audit code against conventions and report findings.
MANDATORY: All output artifacts (review reports, findings, recommendations) MUST be written in en-US. Never mix languages. Flag any mixed-language artifacts as a convention violation.
Convention Checklist
Service Providers
- Providers extend
SageServiceProvider register()only contains bindingsboot()contains hooks and initialization- Dependencies injected via constructor
ACF Blocks & Fields
- Blocks created via
acf:blockgenerator with()returns only data the view needsfields()uses Builder API- Block views use
$variablenotget_field() with()uses field names (get_field('title')) — ACF Composer sets context automatically- Field keys (
field_hero_title) are only needed when writing raw blockdataattributes via WP-CLI or Gutenberg JSON — never inwith()
Blade Templates
- Composers for data injection
- Components for reusable UI
- No business logic in views
- Proper layout inheritance
Routes & Controllers
- Clean route declarations
- Thin controllers
- Acorn Routes over
register_rest_route()
Frontend
- Tailwind v4 CSS-first approach — no
tailwind.config.js - Design tokens declared in
@themeblock ofapp.css - ZERO arbitrary values in Blade templates — any
[#...],[rgba...],[px...],[em...]class is a Critical issue. Grep:\[#,\[rgba,\[px,\[eminresources/views/**/*.blade.php - R-css-vars — CSS variable cascade: Grep for
match($tone)returning Tailwind color classes, or hardcoded color utilities (text-gray-*,bg-brand-*,text-white) directly on<h2>,<p>,<span>elements. Colors must come from--block-*CSS custom properties, not from conditional PHP logic or hardcoded utilities in the view. Each match is Critical. Grep:match\(\$andclass=".*text-(gray|brand|white)inresources/views/blocks/. - Assets via
@vite()orVite::asset() - Editor styles included
- Font utilities use
--font-sans/--font-heading(NOT--font-family-*which is Tailwind v3 syntax)
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.
- 11d ago First seen · 93 lines · 41 tokens per session scan A e49c7ff4336b
superpowers-sage:sage-reviewer is an agent published in the GitHub repository hekivo/superpowers-sage (13 stars, last pushed 3mo ago), licensed MIT. It adds 41 tokens to every session and 1,067 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
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
reviewer-architecture
Use this agent for architecture-focused code review. Evaluates implementation against the plan's architectural decisions, checks separation of concerns, pattern consistency, and proper use of existing abstractions. Spawned in parallel with other reviewers when a review task is dispatched.