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 Uxcel-Lab/product-skills --skill product-reviewgit clone --depth 1 https://github.com/Uxcel-Lab/product-skillsWrote 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/uxcel-lab/product-skills/product-review)<a href="https://agentmods.dev/skills/uxcel-lab/product-skills/product-review"><img src="https://agentmods.dev/badge/skills/uxcel-lab/product-skills/product-review/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/uxcel-lab/product-skills/product-review"><img src="https://agentmods.dev/badge/skills/uxcel-lab/product-skills/product-review.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.00100 | $0.01172 |
| Opus 5 | $0.00050 | $0.00586 |
| Sonnet 5 | $0.00020 | $0.00234 |
| Haiku 4.5 | $0.00010 | $0.00117 |
Grade A, and why
pm-product-review 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 12d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Review (PM Orchestrator) Skill
How this skill behaves (read first)
This is the front door for holistic PM-artifact review. It is the executable form of
docs/orchestration-policy.md applied to PM work: it routes by artifact type to the
relevant audits rather than firing all of them, auto-runs the one always-relevant lens
(assumption rigor), and returns one prioritized report.
PM work has no "design system" suppression case, but it has the same two failures to avoid: a vague "looks good" review, and forcing every PM audit onto a document that only needs one.
When NOT to use this skill: if the user named a specific audit ("run spec-quality", "check my OKR metric validity"), skip this orchestrator and invoke that one directly. Explicit scope overrides orchestration.
Step 0 — Establish context (once)
- Artifact type — spec/PRD, OKRs/KPIs, roadmap, prioritization, vision/strategy, GTM. This is the primary router. Infer it from the document; ask only if genuinely ambiguous.
- Primary goal — what decision this artifact is meant to support (used for conflict resolution and prioritization).
Step 1 — Auto-run the always-relevant lens (Tier A)
pm-assumption-rigor-audit— runs whenever the artifact rests on unproven assumptions, which is nearly always true for PM work. It's cheap, high-leverage, and artifact-agnostic.
Each audit is named by its installable skill
name. Invoke one only if that skill is installed; if one isn't, list it under "available but not run" in the report and don't block — this orchestrator degrades to whichever audits are present.
Step 2 — Route by artifact type (Tier B — run the matching one, offer adjacent ones)
| Artifact | Primary audit | Adjacent lenses to offer |
|---|---|---|
| Spec / PRD | pm-spec-quality-audit |
pm-assumption-rigor-audit (auto), pm-decision-quality-audit |
| OKRs / KPIs / metrics | pm-okr-metric-validity-audit |
pm-assumption-rigor-audit (auto) |
| Roadmap / prioritization | pm-prioritization-rigor-audit |
pm-decision-quality-audit, pm-assumption-rigor-audit (auto) |
| Vision / strategy | pm-decision-quality-audit |
pm-assumption-rigor-audit (auto) |
| GTM plan | pm-decision-quality-audit |
pm-assumption-rigor-audit (auto) |
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.
- 12d ago First seen · 111 lines · 100 tokens per session scan A fccb32719a40
pm-product-review is a skill published in the GitHub repository Uxcel-Lab/product-skills (12 stars, last pushed 2mo ago), licensed MIT. It adds 100 tokens to every session and 1,172 once invoked, about $0.0005 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
azure-devops
Manage Azure DevOps projects, work items, repos, PRs, pipelines, wikis, test plans, security alerts, variable groups, environments/approvals, branch policies, and attachments. Use when user asks to: manage sprints, create/update work items, list repos, create PRs, run pipelines, search code, manage wiki pages, check…
atlassian
Manage Jira issues and Confluence wiki pages in Atlassian Cloud. Use when: (1) searching/creating/updating Jira issues with JQL, (2) searching/reading/creating Confluence pages with CQL, (3) managing Jira workflows, transitions, and comments, (4) browsing Confluence spaces and page hierarchies. Supports OAuth 2.1 via…
pm-brainstorm
A guided brainstorming workflow for exploring a new product idea before detailed research or requirements work. It collects basic information about the product, users, and problem through staged questions.
start-super-pm
Use when starting any product management task - automatically detects task type and invokes appropriate PM skill using intelligent routing.
pm-priority
A Chinese-language procedure for ranking several product requests when time or resources are limited. It supports scoring or grouping methods such as RICE, KANO, and MoSCoW to decide what should be done first.
pm-change
A requirements-change workflow for recording a proposed change, assessing its effects, and deciding whether to approve it.