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 aniganti/pm-superpowers --skill verificationgit clone --depth 1 https://github.com/aniganti/pm-superpowersWrote 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/aniganti/pm-superpowers/verification)<a href="https://agentmods.dev/skills/aniganti/pm-superpowers/verification"><img src="https://agentmods.dev/badge/skills/aniganti/pm-superpowers/verification/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/aniganti/pm-superpowers/verification"><img src="https://agentmods.dev/badge/skills/aniganti/pm-superpowers/verification.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00058 | $0.02017 |
| Opus 5.5 | $0.00023 | $0.00807 |
| Sonnet 5.5 | $0.00012 | $0.00403 |
| Haiku 4.5 | $0.00006 | $0.00202 |
Grade A, and why
verification 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verification Before Completion
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE. This skill exists to prevent thin, placeholder-heavy, or internally contradictory strategy artifacts from being shared with stakeholders.
When to Use
Invoke this skill after any document-producing skill (find-your-moat, strategy, competitive-landscape, vrio-analysis, strategic-moat, product-ecosystem, pre-mortem, prioritization, decision-log, stakeholder-alignment, prompt-builder) and before sharing the artifact with stakeholders.
Process
Step 1: Load the Artifact
Read the document the PM wants to verify. The PM may provide:
- A file path to a saved artifact
- The content directly in the conversation
If no artifact is provided, ask the PM to specify which document they want verified.
STOP if no artifact is provided and the PM cannot point to one. There is nothing to verify.
Step 2: Identify the Artifact Type
Determine which skill produced the artifact based on its structure and content:
| Artifact Type | Key Indicators |
|---|---|
| Find your moat (thin pass) | Title "Find Your Moat", Depth: Thin first pass, four scored moat types, four screened Yes/No, filename …-find-moat-<slug>.md |
| Strategy document | Executive summary, strategic pillars, vision/mission, KPIs |
| Competitive landscape | Competitor profiles table, positioning map, whitespace |
| VRIO analysis | VRIO matrix table, V/R/I/O assessments |
| Strategic moat (full) | All 8 moat types rated, ethical check, filename …-moat-<product-name>.md (not …-find-moat-…) |
| Product ecosystem | Value chain diagram, integration opportunities, closed loops |
| Pre-mortem | Tigers/Paper Tigers/Elephants, action plans |
If an artifact could match both moat types, prefer Find your moat (thin pass) when Depth: Thin first pass or …-find-moat-… is present. Do not apply the full Strategic Moat checklist to a thin pass.
Step 3: Run the Verification Checklist
Apply the appropriate checklist based on artifact type.
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 Changed · +7 lines 860239c694bb
- 1mo ago Changed · +13 lines 7b262e401c68
- 1mo ago First seen · 148 lines · 58 tokens per session scan A 4a461b49c036
verification is a skill published in the GitHub repository aniganti/pm-superpowers (49 stars, last pushed 7d ago), licensed MIT. It adds 58 tokens to every session and 2,017 once invoked, about $0.0002 per session on Opus 5.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
meta-ad-manager
Front door and loop owner of a Meta (Facebook/Instagram) ad harness. Reads the brand's ads/ docs, works out which campaign the user means and which stage it is at, hands off to the stage skill that runs it (intake, strategy, creative, launch, checks, fixes, answers), and writes every stage change back to the docs. Use…
where-to-start-situation-save
Step of the where-to-start playbook: saves the founder's answers and the agreed first move with the brand, so later visits and other playbooks don't ask again. Run where-to-start instead; not for direct use.
mass-ulw
Drives dependency-ordered child work through the native workflow tool, each phase's stages defined up front in one run, with retry/amend/send recovery. Use when the user asks for mass-ulw, a DAG of tasks, or fan-out work where some tasks must wait on others.
fde
Keeps the engagement record for client work. Use when they name a client or stakeholder. Use when they debrief a meeting or paste notes. Use when they ask what was agreed. Use when they run a POC, change the client's codebase, prove it on their staging, go live, or need evals before a model acts. Use when they prep a…
audit
Audit an inherited engagement or implementation against its evidence. Use when taking over work or joining mid-project; distinguish verified facts from inherited claims.
board-memo
Draft a board or executive summary of an engagement using outcomes, risks and investment decisions. Use when the sponsor needs to brief senior leadership.