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/hospital-stay-plan)<a href="https://agentmods.dev/rules/mohitagw15856/pm-claude-skills/hospital-stay-plan"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/hospital-stay-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/hospital-stay-plan"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/hospital-stay-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.00125 | $0.01167 |
| Opus 5 | $0.00063 | $0.00583 |
| Sonnet 5 | $0.00025 | $0.00233 |
| Haiku 4.5 | $0.00013 | $0.00117 |
Grade A, and why
hospital-stay-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 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hospital-Stay Plan
A hospital stay is disorienting and high-stakes, and the most dangerous moment is often discharge — sent home confused about medications, follow-ups, and warning signs, which is how people end up readmitted. This helps you (or the person you're caring for) stay organized and informed through the stay, ask the right questions, and — crucially — plan the discharge early so home is actually safe. It's navigation, not medical advice.
What This Skill Produces
- What to bring & organize — essentials, the medication list, key documents (ID, insurance, advance directives, emergency contacts), and a notebook/phone for tracking
- Staying informed — how to keep track of the care team, what's happening and why, and stay involved in decisions (ask who's in charge, what the plan is, what's changed)
- Daily questions — the things to ask each day (the plan, test results, medication changes, expected discharge)
- Early discharge planning — starting the discharge conversation early (not at the last minute): what has to be true for a safe discharge, and what support will be needed at home
- The home-readiness checklist — for after: medications and how to take them, follow-up appointments, warning signs, equipment/help needed, and who to call
- A boundary — this is logistics and advocacy support, not medical advice
Required Inputs
Ask for these if not provided:
- Who & why — yourself or someone you care for, and the reason for the stay (planned surgery vs. emergency)
- The situation — expected length, condition, and who's coordinating
- Home situation — who they'll go home to, and what support exists
- Your role — patient, primary caregiver, or coordinating from afar
- Concerns — specific worries (confusion, mobility, meds, being sent home too soon)
Framework: Organize, Stay Involved, Plan Discharge Early
- Get organized on arrival. Bring the essentials and documents, and start a shared log of the team, meds, and what's happening — the chaos is worst when nothing's tracked.
- Stay informed and involved. Know who's in charge of the care, ask what the plan is and why, and be present for key conversations — patients/families who engage get better coordination.
- Ask the daily questions. Each day: what's the plan, what did tests show, any medication changes, and when might discharge happen — so there are no surprises.
- Plan discharge from early on. The safe-discharge conversation should start days before, not at the door: what needs to be true to go home, what support and equipment will be needed, and how the transition will work.
- Make home ready. Before discharge, nail down the medication plan, follow-ups, warning signs, any home help/equipment, and the who-to-call — the checklist that prevents readmission.
- Stay in your lane. This is logistics and advocacy; clinicians make the medical decisions.
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 · 71 lines · 125 tokens per session scan A 256217ef1a4e
hospital-stay-plan is a cursor rule published in the GitHub repository mohitagw15856/pm-claude-skills (1,357 stars, last pushed yesterday), licensed MIT. It adds 125 tokens to every session and 1,167 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.