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/aniganti/pm-superpowers/verificationnpx 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.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.00058 | $0.01332 |
| Opus 5 | $0.00029 | $0.00666 |
| Sonnet 5 | $0.00012 | $0.00266 |
| Haiku 4.5 | $0.00006 | $0.00133 |
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 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 — 148 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 (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 |
|---|---|
| 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 | 8 moat types with ratings, ethical check |
| Product ecosystem | Value chain diagram, integration opportunities, closed loops |
| Pre-mortem | Tigers/Paper Tigers/Elephants, action plans |
Step 3: Run the Verification Checklist
Apply the appropriate checklist based on artifact type.
Universal Checks (Apply to ALL artifacts)
- Substance over placeholders — Are all sections populated with real content? Flag any "TBD", "TODO", "[fill in]", or suspiciously generic text.
- Evidence traceability — Does every recommendation or conclusion trace back to specific evidence cited in the document? Flag any unsupported claims.
- Internal consistency — Are there contradictions between sections? (e.g., problem statement says "enterprise users" but target market says "SMB")
- Specificity — Are user segments, competitors, metrics, and recommendations specific? Flag any vague or generic language that could apply to any product.
- Actionability — Could a reader take concrete next steps based on this document? Or does it end with vague aspirations?
- Completeness — Are all expected sections present? Cross-reference against the skill's output structure.
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 · 148 lines · 58 tokens per session scan A 4a461b49c036
verification is a skill published in the GitHub repository aniganti/pm-superpowers (47 stars, last pushed 22d ago), licensed MIT. It adds 58 tokens to every session and 1,332 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 skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.