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/digital-death-plan)<a href="https://agentmods.dev/rules/mohitagw15856/pm-claude-skills/digital-death-plan"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/digital-death-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/digital-death-plan"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/digital-death-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.00116 | $0.01471 |
| Opus 5 | $0.00058 | $0.00736 |
| Sonnet 5 | $0.00023 | $0.00294 |
| Haiku 4.5 | $0.00012 | $0.00147 |
Grade A, and why
digital-death-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 12d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Digital Death Plan Skill
Your life is mostly online now, and none of it is in your will. When someone dies, their family routinely loses irreplaceable photos, can't close accounts that keep billing, gets locked out of email (which is the master key to everything), and spends months fighting platform bureaucracy — all avoidable with an afternoon of planning while alive. This skill builds that plan: inventory the digital assets that matter, set up the legitimate access routes (the built-in legacy features, not password-sharing that violates terms and breaks on death), and write your trusted person clear instructions so grief isn't compounded by a login wall.
What This Skill Produces
- A digital asset inventory: accounts and content sorted by what should happen to each — memorialize, transfer, download-then-close, or delete — with the sentimental and the financial both covered
- An access plan using legitimate mechanisms: platform legacy/inactive-account tools (the ones that actually survive death), where credentials live (a password manager's emergency access, not a sticky note), and what your executor is legally entitled to
- Instructions for your person: a plain letter telling your trusted someone what exists, where the keys are, and what you want done — findable, not buried
- A "what to protect" note: the accounts that keep charging, the ones with real money, the irreplaceable photos, and the ones you'd want closed for privacy
Required Inputs
Ask for (if not already provided):
- The digital footprint: email(s), photo/cloud storage, social media, financial and crypto, subscriptions, domains/websites, gaming, anything with money or memories
- Who the trusted person / executor is, and how tech-comfortable they are
- What the user wants for the sensitive stuff — memorialize socials or delete? who gets the photos? anything to be closed privately without others seeing?
- Whether there's a will/executor already, so this plugs into it rather than floating
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.
- 12d ago First seen · 120 lines · 116 tokens per session scan A b0e89f1468f5
digital-death-plan is a cursor rule published in the GitHub repository mohitagw15856/pm-claude-skills (1,352 stars, last pushed 3d ago), licensed MIT. It adds 116 tokens to every session and 1,471 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-08-30.
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.