phuryn/pm-skills is a marketplace of reusable skills, commands, and plugins that guide AI assistants through product-management work such as discovery, strategy, planning, metrics, launches, and growth. It is for product managers and teams using Claude Code, Cowork, or compatible assistants. The catalogue entries are the project's own workflows and extensions.
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.
git clone --depth 1 https://github.com/phuryn/pm-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/commands/phuryn/pm-skills/ship-check)<a href="https://agentmods.dev/commands/phuryn/pm-skills/ship-check"><img src="https://agentmods.dev/badge/commands/phuryn/pm-skills/ship-check/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/commands/phuryn/pm-skills/ship-check"><img src="https://agentmods.dev/badge/commands/phuryn/pm-skills/ship-check.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.00044 | $0.01927 |
| Opus 5.5 | $0.00018 | $0.00771 |
| Sonnet 5.5 | $0.00009 | $0.00385 |
| Haiku 4.5 | $0.00004 | $0.00193 |
Grade A, and why
ship-check 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 15d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ship-check -- Is This Safe to Ship?
Your AI wrote the code. This command answers the question you actually have — is it safe to ship? — by running the full shipping sequence and compiling the results into one reviewer-ready packet a human can sign off on.
/ship-check does not replace the specialist commands. It coordinates them and produces the final artifact none of them produce alone: the shipping packet.
Invocation
/ship-check
/ship-check the payments service
/ship-check supabase/functions
The shipping sequence
Run on $ARGUMENTS (or the whole repository if empty). Each step builds on the last — the ordering is the point, because every audit is only as good as the documented intent it can compare the code against.
Step 1: Document the system
Ensure the system docs exist and are current (run /document-app if they're missing or stale). Apply the shipping-artifacts skill, including its Locations and names rule (the repo's own docs setup first, the plugin's defaults only where it has none) — the core set (architecture, flows, permissions, variables) plus any conditional docs that apply (emails, cron, seo, automation). These docs are the intended-state baseline for everything that follows.
Step 2: Wire the agent operating context
Create or refresh the repo's agent instruction file derived from the system docs — the operating instructions the next AI coding agent inherits: what the system is, the trust boundaries, what may and may not be touched, where the guardrails are. This is a different artifact from the system docs: instructions, not description.
Follow the structure the repo already has. If one file only imports or points to the other — a CLAUDE.md that is just @AGENTS.md, say — edit the file it points to and leave the pointer alone. If only one of CLAUDE.md and AGENTS.md exists, edit that one. Only in a repo with neither, create CLAUDE.md and a thin AGENTS.md pointing to it.
Step 3: Correctness review
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.
- 15d ago Changed · +2 lines e23a6ffd1111
- 1mo ago Changed · +30 lines · +10 tokens per session 954007285647
- 1mo ago First seen · 78 lines · 34 tokens per session scan A 7c49cdd447da
ship-check is a command published in the GitHub repository phuryn/pm-skills (27,375 stars, last pushed 9d ago), licensed MIT. It adds 44 tokens to every session and 1,927 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 commands, from other repositories
brief-me
Get briefed — loads your full memory, pulls live state from all connected tools, surfaces risks, staleness, upcoming milestones, and gives you a prioritized briefing so you're never starting blank.
design-ai-feature
Design an AI-powered feature end-to-end — model selection, prompt architecture, eval framework, failure modes, cost modeling, and improvement flywheel.
competitive-intel
Run a competitive intelligence analysis — landscape mapping, battlecards, 7 Powers moat comparison, positioning gaps, and monitoring plan.
discover
Run a full discovery cycle — problem framing, JTBD demand-side analysis, assumption mapping, opportunity sizing, and OST mapping — from a rough idea to validated opportunity.
setup-metrics
Set up your metrics framework — North Star selection, funnel definition, dashboard structuring, and A/B test design for your key bets.
plan-launch
Plan a full go-to-market launch — positioning, messaging hierarchy, ICP definition, launch timeline, rollback plan, and post-launch measurement.