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/sibling-care-summit)<a href="https://agentmods.dev/rules/mohitagw15856/pm-claude-skills/sibling-care-summit"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/sibling-care-summit/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/sibling-care-summit"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/sibling-care-summit.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.00126 | $0.01518 |
| Opus 5 | $0.00063 | $0.00759 |
| Sonnet 5 | $0.00025 | $0.00304 |
| Haiku 4.5 | $0.00013 | $0.00152 |
Grade A, and why
sibling-care-summit 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 8d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sibling Care Summit Skill
Parent-care conflict between siblings is rarely about the parent — it's about 1994. The sister who lives nearby slides into everything-by-default; the brother abroad sends money and gets called uninvolved; the family group chat holds three parallel arguments and zero decisions. The summit is the alternative: one structured conversation held before the crisis (or early in it), where the work is inventoried honestly, divided fairly — fair meaning proportional to real capacity, never split-equally-on-paper — and written down, because unwritten care agreements dissolve into the default sibling doing everything and resenting everyone.
What This Skill Produces
- A summit agenda (90 minutes, video counts): parents' current reality → what they want → the work inventory → the division → decision rules → the memo
- The care-share worksheet: every recurring task with its real weekly cost in hours/money/emotional load, and the three currencies siblings can pay in — time, money, and coordination — counted as equally real
- Decision rules written while everyone's calm: what needs all siblings, what the on-the-ground sibling just decides, what the parents still own (most things, longer than the family assumes)
- The family memo: one page, who does what, revisit date — the document that replaces the group-chat archaeology
- De-escalation moves for the two classic derailments: the ledger of 1994, and "you're not here, you don't get a vote"
Required Inputs
Ask for (if not already provided):
- The cast: siblings (and partners-who-do-care-work), where each lives, real constraints (jobs, kids, money, health) — and the honest current split of who does what
- The parents: current needs (or the approaching ones), what they've said they want, how much they know about this meeting happening — the parents are participants in their own lives; the summit plans support, it doesn't dispose of them
- The friction, honestly: old roles, money asymmetries, the sibling who won't engage
- What's triggering this now
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.
- 8d ago First seen · 133 lines · 126 tokens per session scan A ac54c348d9b6
sibling-care-summit is a cursor rule published in the GitHub repository mohitagw15856/pm-claude-skills (1,357 stars, last pushed today), licensed MIT. It adds 126 tokens to every session and 1,518 once invoked, about $0.0006 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.