PM Skills is a collection of plain-Markdown instructions that teach AI assistants structured methods for handling professional, personal, and life-admin tasks. People use it with Claude, ChatGPT, Gemini, Cursor, Codex, and other supported agents for work such as writing product requirements, reviewing documents, or planning difficult situations.
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/mohitagw15856/pm-claude-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/mohitagw15856/pm-claude-skills/design-review)<a href="https://agentmods.dev/commands/mohitagw15856/pm-claude-skills/design-review"><img src="https://agentmods.dev/badge/commands/mohitagw15856/pm-claude-skills/design-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/commands/mohitagw15856/pm-claude-skills/design-review"><img src="https://agentmods.dev/badge/commands/mohitagw15856/pm-claude-skills/design-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.00024 | $0.00652 |
| Opus 5 | $0.00012 | $0.00326 |
| Sonnet 5 | $0.00005 | $0.00130 |
| Haiku 4.5 | $0.00002 | $0.00065 |
Grade A, and why
design-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.
What it actually says
Run the Design Review workflow recipe for: $ARGUMENTS
This is a chain of skills. Run each stage in order and carry every stage's output forward as context for the next. Open with a one-line plan of the 4 stages, then ask once for essential missing inputs (the actual hex values or a URL, the target WCAG level, whether it will ever be printed, who signs off). Don't re-ask between stages.
Before stage 2, measure. A design review that assesses contrast by eye is an opinion with a standards reference attached. If you have a URL or hex values, run these first and carry the numbers through every stage:
npx --yes notugly spec <url> # palette, type scale, radii — what it is made of
npx --yes notugly onepager <url> --out review.html # every pairing, with the nearest passing colour
npx --yes notugly vision <url> # colours that merge for colour-blind viewers
Deterministic, zero dependencies, no model call. If you only have a screenshot, say so explicitly in the output — an inferred ratio is not a finding.
Run each stage under a clear ## Stage N — <name> heading:
- React honestly — apply the
design-critiqueskill: what the design is trying to do, where it succeeds, and where intent and execution diverge. Do this before the measurements so the critique is about the design rather than about its contrast ratios. - Measure what can be measured — apply the
accessibility-auditskill, filling every contrast row from thenotuglyoutput above rather than assessing it. Flag explicitly which findings are computed and which are judgement. - Check the system behind it — apply the
design-system-auditskill: is this a one-off, or does it reveal a token problem? Runnpx notugly tokens <file>if a token file exists; it names failing pairs semantically (color.text.danger on surface.default is 2.99:1), which turns a vague note into a bug with an owner. - Hand it over — apply the
design-handoff-briefskill: the decisions, the measured values, and the open questions, in the form an engineer can build from.
Close with a one-page verdict: the three things to fix before ship, the measured evidence for each, and the split between find-and-replace fixes and fixes that need a design decision. That split is the whole reason this recipe exists — "twelve accessibility issues" gets deferred; "nine are a find-and-replace and three need Priya to pick a colour" gets scheduled.
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 · 28 lines · 24 tokens per session scan A 39d618e4cd1e
design-review is a command published in the GitHub repository mohitagw15856/pm-claude-skills (1,357 stars, last pushed today), licensed MIT. It adds 24 tokens to every session and 652 once invoked, about $0.0001 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 commands, from other repositories
copy-user
Copies a user's Chili Piper workspace and team memberships (and, optionally, product licenses) to another existing user — for onboarding onto an existing territory or replacing a departing rep.
check-availability
Checks why a rep or team is showing no available slots — diagnoses calendar connectivity, working hours, meeting limits, and distribution membership to find the specific blocker.
design-handoff
Prepare a complete handoff package for engineering — Vuetify constraint check followed by handoff document generation.
design-qa
Run a pre-handoff quality assurance check on a completed design.
design-system-check
Scan the design system to find what UI components already exist before designing new ones.
microcopy-writer
Write or review UI copy — button labels, error messages, empty states, tooltips, confirmation dialogs.