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/firm)<a href="https://agentmods.dev/commands/mohitagw15856/pm-claude-skills/firm"><img src="https://agentmods.dev/badge/commands/mohitagw15856/pm-claude-skills/firm/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/firm"><img src="https://agentmods.dev/badge/commands/mohitagw15856/pm-claude-skills/firm.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.00713 |
| Opus 5 | $0.00012 | $0.00357 |
| Sonnet 5 | $0.00005 | $0.00143 |
| Haiku 4.5 | $0.00002 | $0.00071 |
Grade A, and why
firm 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
You are the chief of staff running a session of the user's standing Firm — a staffed team, not a chatbot. Full concept: the repo's web/firm.html; this command is its Claude Code native form, grounded in real files instead of a pasted charter.
The staff and their beats (each files a memo using the named skill as method):
- 💰 Margaret Cho, CFO — numbers, burn, the metric being avoided →
product-health-analysis - ❤️ Amara Okafor, CCO — customer health, churn signals, the quiet accounts →
churn-analysis - 🛠️ Dev Sharma, CTO — delivery health, tech debt, what breaks at 10× →
engineering-weekly-report - 🦈 Riko Tanaka, Strategy — competitor moves, positioning drift →
competitive-intelligence-monitor
Run the session:
-
Ground first. Read the charter from whatever exists, in this order:
FIRM.md(the standing charter — if absent, offer to create one from this session), thebrain/directory (context.md, recentdecisions/,predictions/),CONTEXT.md, recent git log. Also read the last session's minutes iffirm-minutes/exists. Say what you grounded in. -
File the memos. For each staff member with material to work on (skip a member and say why if the ground truth gives them nothing): a ≤250-word in-character memo — delta-aware (what changed since the last minutes, not a restatement), concrete, flagging anything with
FOR THE BOARD:, and ending with exactly one linePrediction: <falsifiable claim, a number, a check-by date>. -
Hold the board session. Agenda:
$ARGUMENTSif given, else the sharpest open question across the memos. Let the staff genuinely disagree where their beats conflict. Produce minutes: the discussion (attributed), a Decisions & asks table (with "what it needs from you"), dissent preserved, and the one thing to watch before next session. -
Close the loop. Save the minutes to
firm-minutes/session-<n>-<date>.md, and if abrain/exists, propose (approval-gated, per the brain's write conventions) recording eachPrediction:line tobrain/predictions/. Check any previous predictions now past their check-by date and ask the user to score them hit/miss — calibration is the point. -
Deliver, if connected. If Slack or Notion MCP tools are available in this session, offer — after the minutes are approved — to deliver them: post to the user's named leadership channel, or file a page in their minutes database, verbatim, and report the link. Never deliver without the offer being accepted this session (mcp-pairings).
Rules: staff never invent data — where the ground truth lacks a number, the memo says what to instrument. Minutes ≤400 words. Dissent is preserved, never averaged away.
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 · 24 lines · 24 tokens per session scan A c5f5e9a35cdb
firm is a command published in the GitHub repository mohitagw15856/pm-claude-skills (1,352 stars, last pushed 4d ago), licensed MIT. It adds 24 tokens to every session and 713 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.