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/commands/hekivo/superpowers-sage/sage-status)<a href="https://agentmods.dev/commands/hekivo/superpowers-sage/sage-status"><img src="https://agentmods.dev/badge/commands/hekivo/superpowers-sage/sage-status/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/commands/hekivo/superpowers-sage/sage-status"><img src="https://agentmods.dev/badge/commands/hekivo/superpowers-sage/sage-status.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.00000 | $0.00262 |
| Opus 5 | $0.00000 | $0.00131 |
| Sonnet 5 | $0.00000 | $0.00052 |
| Haiku 4.5 | $0.00000 | $0.00026 |
Grade A, and why
sage-status 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 10d 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
/sage-status
Reports Lando health, stack versions, active plan, and design tools for the current Sage project.
What it runs
lando info— container status for each service.- Key stack versions: WordPress, PHP, Acorn, Node.
- Active plan detection: first
docs/plans/*/plan.mdfile withstatus: in-progress. - Design tools:
node scripts/detect-design-tools.mjsfrom the plugin root.
Output format (≤ 20 lines total)
### Lando Status
<output of `lando info --format=table` trimmed to service + status>
### Stack Versions
WordPress: <lando wp core version>
PHP: <lando php -r "echo PHP_VERSION;">
Acorn: <lando theme-composer show roots/acorn | grep versions>
Node: <lando node --version>
### Active Plan
<plan directory name or "No active plan found">
### Design Tools
<node scripts/detect-design-tools.mjs — single-line summary>
Instructions
Run each command with lando <cmd>. If a command fails, show "unavailable" for that entry. Present all four sections within 20 output lines total.
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.
- 10d ago First seen · 34 lines · 0 tokens per session scan A 61de8ba8660c
sage-status is a command published in the GitHub repository hekivo/superpowers-sage (13 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 262 tokens. 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.