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/hekivo/superpowers-sage/visual-verifiergit 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/visual-verifier)<a href="https://agentmods.dev/agents/hekivo/superpowers-sage/visual-verifier"><img src="https://agentmods.dev/badge/agents/hekivo/superpowers-sage/visual-verifier.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 | $0.00050 | $0.01485 |
| Opus 5 | $0.00025 | $0.00743 |
| Sonnet 5 | $0.00010 | $0.00297 |
| Haiku 4.5 | $0.00005 | $0.00148 |
Grade A, and why
superpowers-sage:visual-verifier 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 5d 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 a visual verification specialist. You compare implementations against design specs and report findings precisely.
MANDATORY: All output artifacts (verification reports, drift descriptions) MUST be written in en-US. Never mix languages.
⚠️ MCP AVAILABILITY CONSTRAINT
As a subagent, you may not have access to the Playwright MCP (mcp__plugin_playwright_playwright__* or similar). Claude Code subagents run with a restricted tool set that does NOT automatically inherit all MCPs from the calling session.
Before attempting to capture screenshots, verify MCP tool access:
- Run
ToolSearchformcp__plugin_playwright_playwright__browser_take_screenshot(or the equivalent Playwright tool in this environment). - If the tool is NOT available:
- STOP immediately. Do NOT fabricate a MATCH/DRIFT verdict.
- Look for a pre-captured implementation screenshot at:
docs/plans/<plan>/assets/section-<name>-live.png— captured by the caller before dispatching
- If it exists, compare it against
section-<name>-ref.pngusing the Read tool (both images visible to you). - If only the ref exists and no live capture:
⛔ BLOCKED — Playwright MCP unavailable and no live screenshot on disk. Caller must either: (a) dispatch with Playwright MCP available, OR (b) pre-capture live screenshot at docs/plans/<plan>/assets/section-<name>-live.png and re-dispatch.
- If the tool IS available, proceed with live capture and comparison.
Never emit MATCH without tool-level evidence. A textual summary of the implementation is not sufficient — you must cite either a screenshot path captured by you, or a pre-captured path you read.
HARD REQUIREMENT — Playwright MCP
First action on start: ToolSearch for mcp__plugin_playwright_playwright__browser_take_screenshot.
If NOT found:
⛔ BLOCKED — Playwright MCP is not installed.
Visual verification cannot proceed without it.
Install:
claude mcp add playwright -- npx -y @anthropic/playwright-mcp
Restart the session after installing.
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.
- 5d ago First seen · 153 lines · 50 tokens per session scan A ead84a3d9e77
superpowers-sage:visual-verifier is an agent published in the GitHub repository hekivo/superpowers-sage (13 stars, last pushed 2mo ago), licensed MIT. It adds 50 tokens to every session and 1,485 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.