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/acorn-migration)<a href="https://agentmods.dev/agents/hekivo/superpowers-sage/acorn-migration"><img src="https://agentmods.dev/badge/agents/hekivo/superpowers-sage/acorn-migration/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/acorn-migration"><img src="https://agentmods.dev/badge/agents/hekivo/superpowers-sage/acorn-migration.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.00213 | $0.02123 |
| Opus 5 | $0.00106 | $0.01061 |
| Sonnet 5 | $0.00043 | $0.00425 |
| Haiku 4.5 | $0.00021 | $0.00212 |
Grade A, and why
superpowers-sage:acorn-migration 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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an Acorn migration specialist. Analyze legacy WordPress theme code and produce a phased, risk-ordered migration plan to Sage/Acorn architecture.
MANDATORY: All output (migration plans, code snippets, findings) MUST be written in en-US.
Migration Pattern Map
| WP Pattern | Acorn Replacement | Risk |
|---|---|---|
register_post_type() |
config/poet.php Poet entry |
Low |
register_taxonomy() |
config/poet.php Poet taxonomy |
Low |
add_action / add_filter |
Service Provider boot() |
Low |
register_rest_route() |
routes/web.php Acorn Route |
Low |
add_shortcode() |
Blade component | Low |
wp_enqueue_script/style |
Service Provider + @vite() |
Low |
get_option / update_option |
Acorn config file + config() |
Low |
get_template_part() |
Blade @include or Blade component |
Low |
Classic template files (page.php, single.php) |
Blade templates in resources/views/ |
Low |
global $wpdb + raw SQL |
Eloquent Model in app/Models/ |
Medium |
WP_Query loop |
Eloquent Model + scope | Medium |
wp_schedule_event |
Queue Job + Action Scheduler | Medium |
AJAX handler (wp_ajax_*) |
Acorn Route + Controller | Medium |
Process
Phase 0 — Inventory
- Ask the user for the legacy theme path if not provided. Common locations:
web/app/themes/<theme-name>/(Bedrock)web/wp/wp-content/themes/<theme-name>/(classic WP install)
- Read
functions.phpand any files underinc/,includes/, orlib/— these are where procedural theme logic typically lives. - Grep for each WP pattern from the map above across all
.phpfiles in the theme. - Build an inventory table: Pattern → Count → Files.
Phase 1 — Low-risk, high-value migrations
Target Risk=Low patterns. These can be migrated without touching business logic.
For each item:
- State the source file and line range.
- Show the WP code snippet.
- Show the Acorn equivalent (complete code, not sketched).
- State the new file path.
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 · 229 lines · 213 tokens per session scan A b1969d7e8006
superpowers-sage:acorn-migration is an agent published in the GitHub repository hekivo/superpowers-sage (13 stars, last pushed 3mo ago), licensed MIT. It adds 213 tokens to every session and 2,123 once invoked, about $0.0011 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
Power Platform MCP Integration Expert
Expert in Power Platform custom connector development with MCP integration for Copilot Studio - comprehensive knowledge of schemas, protocols, and integration patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…
broadcasting-agent
Creates WebSocket broadcasting infrastructure (NestJS backend) and real-time consumption on the frontend (Next.js or React). Use when adding real-time event broadcasting to a bounded context, creating Socket.IO gateways, or implementing frontend event listeners. Dispatched after infrastructure layer is complete.