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/rules/mohitagw15856/pm-claude-skills/care-decision-family-meeting)<a href="https://agentmods.dev/rules/mohitagw15856/pm-claude-skills/care-decision-family-meeting"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/care-decision-family-meeting/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/rules/mohitagw15856/pm-claude-skills/care-decision-family-meeting"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/care-decision-family-meeting.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.00146 | $0.01278 |
| Opus 5 | $0.00073 | $0.00639 |
| Sonnet 5 | $0.00029 | $0.00256 |
| Haiku 4.5 | $0.00015 | $0.00128 |
Grade A, and why
care-decision-family-meeting 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 9d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Care-Decision Family Meeting
Big care decisions — where a parent lives, what care they need, who pays, who does what — bring out every old family dynamic, and often end in a fight, a stalemate, or one exhausted person deciding alone and resenting it. A structured family meeting changes that. This gives you the agenda, preparation, ground rules, and facilitation to make it a shared, informed decision — including the person being cared for — with clear next steps. Not legal, medical, or financial advice.
What This Skill Produces
- A meeting agenda — a clear structure (the situation, the options, everyone's input, working to a decision, next steps) so it doesn't spiral
- Preparation — the facts, options, and information to gather beforehand (a meeting without shared facts is just an argument), and getting everyone's views in advance
- Ground rules — norms to keep old sibling dynamics, blame, and one loud voice from derailing it (one person speaks at a time, focus on the parent's needs, no re-litigating history)
- Including the person — how to involve the one being cared for in the decision about their own life, to the extent they can
- Disagreement navigation — ways to work through the common conflicts (who does more, who pays, differing views on the parent's needs) toward an actual decision
- Next steps with owners — concrete actions, who does what, and when to revisit — so the meeting produces action, not just talk
- A boundary — this facilitates the decision; the medical, legal, and financial specifics need professionals
Required Inputs
Ask for these if not provided:
- The decision — what needs deciding (living situation, care level, finances, division of duties)
- Who's involved — the family members, their locations, and the dynamics
- The person being cared for — their needs, wishes, and capacity to participate
- The disagreements — where views differ or tension exists
- The facts available — what's known vs. needs gathering (costs, options, medical input)
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.
- 9d ago First seen · 74 lines · 146 tokens per session scan A ef8d3b1f71e6
care-decision-family-meeting is a cursor rule published in the GitHub repository mohitagw15856/pm-claude-skills (1,357 stars, last pushed yesterday), licensed MIT. It adds 146 tokens to every session and 1,278 once invoked, about $0.0007 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-09-03.
Other cursor rules, from other repositories
cursor
Always-on my-adhd-caveman. Off with "stop adhd-caveman" or "normal mode".
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.