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/install-pluginnpx skills add hekivo/superpowers-sage --skill install-plugingit 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/install-plugin)<a href="https://agentmods.dev/skills/hekivo/superpowers-sage/install-plugin"><img src="https://agentmods.dev/badge/skills/hekivo/superpowers-sage/install-plugin.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.00074 | $0.00794 |
| Opus 5 | $0.00037 | $0.00397 |
| Sonnet 5 | $0.00015 | $0.00159 |
| Haiku 4.5 | $0.00007 | $0.00079 |
Grade A, and why
superpowers-sage:install-plugin 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 6d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Install Plugin (Composer + Lando)
Install WordPress plugins through Composer only.
Announce at start: "I'm using the install-plugin skill to install this plugin with Composer inside Lando."
Inputs
$ARGUMENTS
Rules
- Never use
wp plugin installfor new plugin installation. - Always run
composerthrough Lando:lando composer .... - Install at project root
composer.json(WordPress/plugin level), not themecomposer.json. - If plugin activation is requested, use
lando wp plugin activate <slug>after Composer install.
Procedure
1) Validate context
- Confirm this is a Lando WordPress project (
.lando.ymland rootcomposer.jsonexist). - Read
skills/sage-lando/references/wordpress-composer.md. - Ensure
wp-packages.orgrepository exists:
lando composer config repositories.wp-packages composer https://repo.wp-packages.org
2) Route by argument type
Case A: Local zip (*.zip)
- Resolve path from
$ARGUMENTS. - If zip is outside project root, copy to
./packages/<filename>.zip. - Derive slug from filename:
plugin-name.zip-> packagelocal/plugin-name, typewordpress-pluginmu-plugin-name.zip-> packagelocal/plugin-name, typewordpress-muplugin
- Add/update a
type: packagerepository entry in rootcomposer.jsonpointing to./packages/<filename>.zip. - Install with Composer:
lando composer require local/plugin-name
Case B: Package name already provided (vendor/name)
- If argument already matches
vendor/name, install directly:
lando composer require vendor/name
- If it starts with
wp-plugin/, no extra conversion is needed.
Case C: Plugin slug or human name
- Normalize to a slug candidate (lowercase, dashes).
- Try package
wp-plugin/<slug>. - If uncertain or missing, search on
https://wp-packages.org/and map to the exact slug. - Install:
lando composer require wp-plugin/<slug>
3) Verify installation
# Composer package installed
lando composer show wp-plugin/<slug>
# WordPress sees plugin
lando wp plugin list
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.
- 6d ago First seen · 119 lines · 74 tokens per session scan A 39fef44d53d6
superpowers-sage:install-plugin is a skill published in the GitHub repository hekivo/superpowers-sage (13 stars, last pushed 2mo ago), licensed MIT. It adds 74 tokens to every session and 794 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…