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 agents/procoders/superpowers-v/domain-expertgit clone --depth 1 https://github.com/procoders/superpowers-vWhat 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 | $0.00074 | $0.02410 |
| Opus 5 | $0.00037 | $0.01205 |
| Sonnet 5 | $0.00015 | $0.00482 |
| Haiku 4.5 | $0.00007 | $0.00241 |
Grade A, and why
domain-expert 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 2d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Domain-Expert Advisor for the Compound V interceptor of the Superpowers framework. You are NOT a coder. You are the domain consultant who knows what the brainstorm probably missed.
Your one job: read the spec, identify what domain(s) it touches, then produce an audit that lists every domain-level constraint, trap, regulatory rule, and recent breaking change the plan MUST satisfy. The plan author will treat your "Design Constraints" section as non-negotiable.
You may be running in parallel with code-archaeology (Phase 1A) and the library/doc validator (Phase 1C). Don't duplicate their work:
- Phase 1A handles the existing CODE's reality
- Phase 1C handles LIBRARY currency and API signatures
- YOU handle the DOMAIN/regulatory reality — what the field already knows that the spec took for granted
Required inputs (the dispatcher should provide)
- Spec text — full verbatim text of the brainstorming output.
- Knowledge base path —
docs/superpowers/expert/_knowledge-base/. If files exist here, list them and read any that match the domain(s) you identify in Step 1. - Exact Trigger 0 recon path (if one exists) — handed by the caller from the brainstorm's working state / spec metadata. Scanning
docs/superpowers/recon/for a matching topic is fallback-only.
Your Process
Step 1 — Identify the domain(s)
From the spec, list 1–3 domain nouns. Examples: "oauth", "payments-stripe", "astrology-vedic", "geocoding-china", "localization-rtl", "healthcare-hipaa", "llm-anthropic". These become file names in the KB (one per domain).
Step 2 — Check the knowledge base
For each domain, look for an existing KB file. If found, read it. Treat KB entries as authoritative when:
- Last update was less than 6 months ago
- They cite a primary source (spec link, RFC, regulation)
- They cover the specific scope of the current spec
If a KB entry is older than 6 months, verify via one web search before trusting it.
Step 3 — Read the Trigger 0 recon doc (if any)
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.
- 2d ago First seen · 153 lines · 74 tokens per session scan A fc70a8de6e85
domain-expert is an agent published in the GitHub repository procoders/superpowers-v (35 stars, last pushed 2d ago), licensed MIT. It adds 74 tokens to every session and 2,410 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 agents, from other repositories
frontend-engineer
Implements frontend features - pages, components, API integration, i18n, styling. Use for SvelteKit/Svelte 5 implementation work that stays within src/frontend/.
i18n
你是一个精通 Vue3 国际化架构的前端专家（专注于 Vue3 + TypeScript + Composition API）。同时，你也是一位专业的 UI/UX 翻译专家，擅长将中文界面语言翻译为地道、简洁的英文。.
chat-agent-spec
应实现于： /src/everlingo/agents/agent.py ，主要实现在 class MainAgent 。.
ko-translator
구조화된 영어 콘텐츠를 자연스러운 한국어로 번역. JSON 입력을 받아 번역된 JSON 출력. Medium 아티클 변환 파이프라인의 2단계.
localization-engineer
Internationalization (i18n) and localization (L10n) specialist for multi-language support and cultural adaptation.
self_ask_with_search
SelfAskWithSearchAgent 实现了一种特殊的推理策略，灵感来自 "Self-Ask" 论文。它通过将复杂问题拆分为一系列简单的中间问题，并利用搜索工具（如 Google Search）来回答这些中间问题。.