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/burnout-recovery-plan)<a href="https://agentmods.dev/rules/mohitagw15856/pm-claude-skills/burnout-recovery-plan"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/burnout-recovery-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/burnout-recovery-plan"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/burnout-recovery-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.00115 | $0.01043 |
| Opus 5 | $0.00057 | $0.00522 |
| Sonnet 5 | $0.00023 | $0.00209 |
| Haiku 4.5 | $0.00012 | $0.00104 |
Grade A, and why
burnout-recovery-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.
Burnout Recovery Plan
Burnout isn't cured by a weekend off — it comes back if the conditions that caused it don't change. Recovery is two-track: immediate relief to stop the freefall, and structural changes to the drivers (unsustainable load, no control, no reward, unfairness, values mismatch). This helps you diagnose your drivers and build a plan you can actually act on — while being clear that severe cases need real support.
What This Skill Produces
- A driver diagnosis — which burnout factors are hitting you (workload, lack of control, insufficient reward, unfairness, community breakdown, values conflict)
- Immediate relief — the first steps to reduce acute strain and create breathing room
- Root-cause changes — the boundary, workload, and role changes (and the conversations with your manager) that address why it happened
- A recovery timeline — honest expectations that recovery takes time and isn't linear
- When it's bigger — a clear flag that severe, persistent burnout — or signs of depression/anxiety — needs a professional
- A sustainability check — how to prevent the slide back
Required Inputs
Ask for these if not provided:
- The signs — exhaustion, cynicism, dread, reduced performance, physical symptoms
- The context — job/role, workload, control, and what specifically drains you
- How long — recent or long-running (affects severity)
- What you can change — leverage at work, financial constraints, support available
- Severity — coping but depleted, or genuinely unable to function
Framework: Relieve, Then Fix The Cause
- Diagnose the drivers. Burnout has known contributors (load, control, reward, fairness, community, values) — identify which are active, because the fix depends on the cause.
- Create immediate relief. Reduce acute strain now — use leave if possible, drop or defer non-essentials, and restore basic rest, movement, and connection.
- Change the root, not just rest. Rest without changing the conditions relapses — plan the boundaries, workload renegotiation, or role/values shifts, including a concrete manager conversation.
- Set realistic timelines. Recovery is gradual and non-linear; frame expectations so a bad day isn't read as failure.
- Know when it's beyond self-help. Persistent, severe burnout or signs of depression/anxiety warrant a doctor or therapist — say this plainly.
- Build sustainability. Put in the ongoing habits and boundaries that stop the slide back.
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 · 115 tokens per session scan A 36e81e002489
burnout-recovery-plan is a cursor rule published in the GitHub repository mohitagw15856/pm-claude-skills (1,357 stars, last pushed yesterday), licensed MIT. It adds 115 tokens to every session and 1,043 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.