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/proofread)<a href="https://agentmods.dev/commands/phuryn/pm-skills/proofread"><img src="https://agentmods.dev/badge/commands/phuryn/pm-skills/proofread/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/proofread"><img src="https://agentmods.dev/badge/commands/phuryn/pm-skills/proofread.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.00015 | $0.00426 |
| Opus 5.5 | $0.00006 | $0.00170 |
| Sonnet 5.5 | $0.00003 | $0.00085 |
| Haiku 4.5 | $0.00002 | $0.00043 |
Grade A, and why
proofread 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 1mo 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.
What it actually says
/proofread -- Grammar & Flow Check
Identify grammar, logical, and flow errors in text. Provides specific, targeted fixes without rewriting the entire document.
Invocation
/proofread [paste text]
/proofread [upload a document]
Workflow
Step 1: Accept Text
Accept text in any form: pasted, uploaded document (DOCX, PDF, markdown), or email draft.
Step 2: Analyze
Apply the grammar-check skill:
Scan for three categories of issues:
Grammar: Spelling, punctuation, subject-verb agreement, tense consistency, article usage Logic: Contradictions, unsupported claims, circular reasoning, unclear references Flow: Awkward transitions, sentence rhythm, paragraph structure, redundancy, readability
Step 3: Report Issues
## Proofread Report
**Text length**: [word count]
**Issues found**: [count by category]
### Issues
#### 1. [Category: Grammar/Logic/Flow]
- **Location**: "[quoted text with issue]"
- **Issue**: [what's wrong]
- **Fix**: "[corrected text]"
[Repeat for each issue]
### Summary
- Grammar: [X] issues
- Logic: [X] issues
- Flow: [X] issues
- Overall quality: [assessment]
Step 4: Offer
- "Want me to apply all fixes and return the cleaned text?"
- "Should I focus on a specific section in more detail?"
Notes
- Fix suggestions should be minimal — change only what's needed, preserve the author's voice
- For non-native English speakers, be especially clear about why a change is suggested
- Don't over-correct style preferences — there's a difference between wrong and different
- For professional documents, also check for tone consistency and audience appropriateness
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.
- 1mo ago First seen · 68 lines · 15 tokens per session scan A bb62a6851c81
proofread is a command published in the GitHub repository phuryn/pm-skills (27,091 stars, last pushed yesterday), licensed MIT. It adds 15 tokens to every session and 426 once invoked, about $0.0001 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-09-15.
Other commands, from other repositories
customer-stories
Kick off, interview for, draft, send for customer review or audit a B2B customer story in one fixed structure, with stats and named quotes checked.
experiment-ideas
Generate several concrete, brain-grounded growth ideas — channel, message, rationale, cost-efficiency — ranked by effort vs. impact.
value-prop-statements
Fan an existing positioning statement out into segment- and channel-specific value-prop copy variants, trace-checked against drift.
pmm-metrics
Define a North Star Metric and capped scorecard, or audit an existing metrics list for sprawl and vanity metrics.
proof-points
Pull proof points from decks/battlecards, register, verify, or audit the claims your messaging relies on — then deepen brain Section 6 argument-hint: ".
product-messaging-playbook
Assemble a Sales/CS-ready messaging playbook for a new product or feature — problem, story, one named competitive comparison, discovery questions, objection handling.