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/ship-an-mcp-server)<a href="https://agentmods.dev/commands/mohitagw15856/pm-claude-skills/ship-an-mcp-server"><img src="https://agentmods.dev/badge/commands/mohitagw15856/pm-claude-skills/ship-an-mcp-server/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/ship-an-mcp-server"><img src="https://agentmods.dev/badge/commands/mohitagw15856/pm-claude-skills/ship-an-mcp-server.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.00019 | $0.00411 |
| Opus 5 | $0.00010 | $0.00205 |
| Sonnet 5 | $0.00004 | $0.00082 |
| Haiku 4.5 | $0.00002 | $0.00041 |
Grade A, and why
ship-an-mcp-server 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 Ship an MCP Server 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 any essential missing inputs (the product's top user jobs, the existing API surface, the riskiest actions, current pricing model). Don't re-ask between stages.
Run each stage under a clear ## Stage N — <name> heading:
- Spec the server — apply the
mcp-server-specskill: a task-shaped toolset (3-10 tools, never an API mirror), auth model, gated actions, the never-exposed list, and the agent test plan. - Audit readiness — apply the
agent-readiness-auditskill across all six surfaces (discovery, docs, API/auth, errors, onboarding, guardrails), quoting the failing artifacts; feed the spec from stage 1 so the audit checks against what will actually ship. - Fix the pricing — apply the
agent-era-pricingskill: the value metric that survives non-human users, tier fences with named gaming vectors, and cannibalisation math on representative cohorts — informed by which tools stage 1 exposed and what usage they'll drive. - Design the oversight — apply the
human-in-the-loop-designskill to every gated action from stage 1: action tiers, the approval budget, escalation rules, and the audit trail.
Close with a one-page rollout summary: the toolset, the top 3 readiness fixes, the pricing decision, and the approval policy — the packet an eng lead and a pricing owner could execute from.
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 · 18 lines · 19 tokens per session scan A cb7a3338e3a4
ship-an-mcp-server is a command published in the GitHub repository mohitagw15856/pm-claude-skills (1,357 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 411 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.
replay
Summarize one Agent Monitor session by id — header plus a concise transcript recap.
manage-scheduling-links
Manages scheduling links (round-robin, admin one-on-one, group, ownership) — list, create, update, delete — with a dry-run plan and confirmation before any write.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.