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/respite-care-plan)<a href="https://agentmods.dev/rules/mohitagw15856/pm-claude-skills/respite-care-plan"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/respite-care-plan/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/respite-care-plan"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/respite-care-plan.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.00144 | $0.01225 |
| Opus 5 | $0.00072 | $0.00613 |
| Sonnet 5 | $0.00029 | $0.00245 |
| Haiku 4.5 | $0.00014 | $0.00122 |
Grade A, and why
respite-care-plan 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Respite-Care Plan
"I can't leave them" is how caregivers burn out — but respite (planned breaks) is exactly what makes long-term caregiving sustainable. The barriers are real: guilt, not trusting anyone else, cost, and the logistics of handing off. This plans a genuine break: who can cover, the handoff so they're set up to succeed, how to get past the barriers, and how to actually rest instead of worrying the whole time — so the break happens and repeats. Not medical advice.
What This Skill Produces
- Coverage options — the realistic ways to get covered for your situation: family/friends, paid in-home respite, adult day programs, or a short-stay facility break, with pros/cons
- A handoff pack — what whoever covers needs to succeed: the routine, medications, contacts, what-ifs, and the person's preferences — so you can actually step away
- Barrier-busting — addressing the specific things stopping you: guilt, not trusting others, cost/funding to look into, and the logistics
- A "actually rest" plan — how to use the break to genuinely recover (and quiet the worry) rather than spend it anxious or doing chores
- A make-it-repeatable setup — turning a one-off into a regular, sustainable rhythm of breaks
- A boundary — logistics support, not medical advice; complex care needs professional respite arrangements
Required Inputs
Ask for these if not provided:
- Who you care for — their needs and how much supervision/care they require
- The break you need — a few hours, a day, or longer
- Who/what's available — family, budget for paid help, local services
- The barrier — guilt, trust, cost, logistics, or "no one else can do it"
- What rest looks like for you — what would actually recharge you
Framework: Arrange, Hand Off, Rest, Repeat
- Find the coverage. Map the realistic options — a family member, paid respite worker, a day program, or a short-stay — matched to the care level and your budget.
- Prepare the handoff. The trust barrier shrinks when whoever covers has a clear pack: routine, medications, contacts, warning signs, and preferences. Set them up to succeed.
- Bust the barriers. Guilt (respite is necessary, not selfish), trust (a prepared, competent stand-in), cost (funding routes to research), and logistics (start small) — address each directly.
- Plan to actually rest. A break spent worrying or catching up on chores isn't respite — decide in advance how you'll genuinely recover, and how to quiet the worry (a check-in call, trusting the pack).
- Make it repeatable. One break isn't enough — set up a regular rhythm so respite is a sustained part of the caregiving, not a rare emergency.
- Get professional help for complex needs. Where care is medically complex, use professional respite services; this handles the planning, not the medical care.
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 · 71 lines · 144 tokens per session scan A a72677835764
respite-care-plan is a cursor rule published in the GitHub repository mohitagw15856/pm-claude-skills (1,352 stars, last pushed 4d ago), licensed MIT. It adds 144 tokens to every session and 1,225 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
publisher
Publish HTML frontend projects to the publishing platform (publisher). Use when the user wants to publish/ship a project, get an access URL, list their published projects, or build an Android APK. No Python required — call the HTTP APIs directly.
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.