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/layoff-first-72-hours)<a href="https://agentmods.dev/rules/mohitagw15856/pm-claude-skills/layoff-first-72-hours"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/layoff-first-72-hours/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/layoff-first-72-hours"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/layoff-first-72-hours.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.01102 |
| Opus 5 | $0.00063 | $0.00551 |
| Sonnet 5 | $0.00025 | $0.00220 |
| Haiku 4.5 | $0.00013 | $0.00110 |
Grade A, and why
layoff-first-72-hours 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 7d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Layoff: First 72 Hours
A layoff is a shock, and the instinct is to either freeze or panic-apply to 100 jobs by nightfall. Neither helps. The first few days are for steadying yourself and handling the time-sensitive, high-value things — the severance terms, benefits continuity, references, and support you're entitled to — before the job search. This lays them out in a calm order.
What This Skill Produces
- A first-days checklist — the practical moves in priority order, spread over days, not a same-day frenzy
- Package review — understanding the severance/redundancy terms, and what may be negotiable before you sign
- Benefits & finances — protecting health coverage, understanding final pay/accruals, and filing for any unemployment/support you're entitled to
- Relationships to secure now — references, recommendations, and contacts while goodwill is fresh
- Emotional footing — permission to feel it, and a note that your worth isn't the layoff
- A bridge to the search — how to transition into job-hunting from a steady base
Required Inputs
Ask for these if not provided:
- The situation — when, whether there's a severance/package, and any documents to sign
- Your finances — runway, obligations, and how urgent income is
- Benefits — health coverage and anything tied to the job
- Region — affects support/unemployment and rights
- Your state — steady enough to plan, or in shock (pace accordingly)
Framework: Steady First, Then The High-Value Moves
- Don't sign or panic-apply immediately. Give yourself a beat. Severance documents can often wait a little, and rushed applications are weak ones.
- Understand (and maybe negotiate) the package. Read the severance/redundancy terms; some elements (notice, payout, references, timing) may be negotiable — consider advice before signing anything binding.
- Protect benefits and cash flow. Sort health coverage continuity, confirm final pay/accrued leave, and file for unemployment/support promptly (these have timelines).
- Secure relationships while warm. Ask for references, LinkedIn recommendations, and keep contacts before people scatter — goodwill fades.
- Tend to your head. A layoff is usually about the business, not your worth — build in support and routine before the search grind.
- Then bridge to the search. Move into job-hunting from a steady, organized base — resume, targets, and outreach — rather than a frightened scramble.
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.
- 7d ago First seen · 72 lines · 126 tokens per session scan A 5211cf5919dc
layoff-first-72-hours is a cursor rule published in the GitHub repository mohitagw15856/pm-claude-skills (1,352 stars, last pushed 3d ago), licensed MIT. It adds 126 tokens to every session and 1,102 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.