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 skills add learn-by-exploration/ai-powerhouse --skill se-lifecyclegit clone --depth 1 https://github.com/learn-by-exploration/ai-powerhouseWrote 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/learn-by-exploration/ai-powerhouse/se-lifecycle)<a href="https://agentmods.dev/skills/learn-by-exploration/ai-powerhouse/se-lifecycle"><img src="https://agentmods.dev/badge/skills/learn-by-exploration/ai-powerhouse/se-lifecycle/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/skills/learn-by-exploration/ai-powerhouse/se-lifecycle"><img src="https://agentmods.dev/badge/skills/learn-by-exploration/ai-powerhouse/se-lifecycle.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.00053 | $0.00964 |
| Opus 5 | $0.00026 | $0.00482 |
| Sonnet 5 | $0.00011 | $0.00193 |
| Haiku 4.5 | $0.00005 | $0.00096 |
Grade A, and why
se-lifecycle 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Systems Engineering Lifecycle (ISO/IEC/IEEE 15288)
Use this when: you're starting a new system, taking over an existing one and don't know where it is in its lifecycle, or you're auditing whether the work covers all 11 Technical processes 15288 expects.
For the full reference, see docs/se-15288.md. This skill is the routing entry point — it answers "given where I am, what tool should I use?"
The 11 Technical processes at a glance
| # | 15288 process | Powerhouse tool | What you produce |
|---|---|---|---|
| 6.4.1 | Stakeholder Needs | mem-mem-search + master-se-systems-engineer |
docs/stakeholder-needs.md |
| 6.4.2 | Requirements Definition | superpowers-writing-plans |
Requirements in the plan's spec section |
| 6.4.3 | Architecture Definition | ecc-architect |
docs/adr/0001-*.md, C4 views |
| 6.4.4 | Implementation | superpowers-subagent-driven-development |
Code + tests + build |
| 6.4.5 | Integration | ws-agent-teams-team-lead |
Integration test report |
| 6.4.6 | Verification | superpowers-test-driven-development, ecc-code-reviewer |
Test report, review log |
| 6.4.7 | Validation | ws-agent-teams-team-review, ecc-verify |
Acceptance evidence per need |
| 6.4.8 | Transition | ws-deployment-validation-config-validate |
Deployment plan + rollback runbook |
| 6.4.9 | Operation | ws-observability-monitoring-monitor-setup |
Runbook, SLOs, alert routing |
| 6.4.10 | Maintenance | ecc-refactor-cleaner, superpowers-systematic-debugging |
Change records, defect log |
| 6.4.11 | Disposal | no harness tool — write docs/disposal-plan.md from the prompt in docs/se-15288.md |
Disposal plan + sanitization evidence |
The other 19 processes (Agreement, Organizational Project-Enabling, Technical Management) are handled by the org and tooling, not by individual engineers — they're outside the scope of "which skill do I run now?"
How to invoke
If you want a guided walkthrough
Invoke the master-se-systems-engineer agent. It will:
- Ask which phase you're currently in
- Run the right Powerhouse tool for that phase
- Capture the 15288-expected artifact
- Gate the next phase on the verification/validation evidence the standard requires
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 · 63 lines · 53 tokens per session scan A ab6ba51822a6
se-lifecycle is a skill published in the GitHub repository learn-by-exploration/ai-powerhouse (2 stars, last pushed 2mo ago), licensed MIT. It adds 53 tokens to every session and 964 once invoked, about $0.0003 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-31.
Other skills, from other repositories
impeccable
Create distinctive, production-grade frontend interfaces with high design quality. Generates creative, polished code that avoids generic AI aesthetics. Use when the user asks to build web components, pages, artifacts, posters, or applications, or when any design skill requires project context. Call with 'craft' for…
open
Boot the session, load context from the vault, and surface what matters.
Self-Review
Spawn a reviewer subagent with 4-6 specific verification questions before declaring non-trivial code work done. Triggers when changes are >30 LOC, multi-file, hot-path, prompt-affecting, or genuinely uncertain. Bad asks produce bad answers — this skill forces structured verification questions, not "is this good?".
Skill Audit
List every installed skill, when it was last invoked, how often, and whether the description still matches the trigger patterns the principal actually uses. Flags dead skills for retirement and frequently-needed-but-missing capabilities for skill creation. Pairs with Caddy.
solution-hunt
When blocked, systematically search for legitimate alternate routes before declaring inability.
sprite-spec
Iris's sprite design specification skill. Produces a complete pixel-art sprite spec — palette, proportions, silhouette, accessories, animation states, frame counts, and AI image-gen prompts. Returns honesty ledger.