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/legacy-letter)<a href="https://agentmods.dev/rules/mohitagw15856/pm-claude-skills/legacy-letter"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/legacy-letter/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/legacy-letter"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/legacy-letter.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.00136 | $0.01443 |
| Opus 5 | $0.00068 | $0.00722 |
| Sonnet 5 | $0.00027 | $0.00289 |
| Haiku 4.5 | $0.00014 | $0.00144 |
Grade A, and why
legacy-letter 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Legacy Letter Skill
A will distributes your things; a legacy letter gives your people the things a will can't — the stories only you remember, what you were proud of, what you're sorry for, the specific reasons you loved them, and the permission to be okay. Also called an ethical will, it's one of the most treasured objects a family can hold, and most people mean to write one and never do because the blank page is too heavy. This skill makes it doable: it interviews gently, finds the true and specific things (not Hallmark platitudes), and shapes them into a letter that sounds unmistakably like the writer — because the voice is the gift.
What This Skill Produces
- A legacy letter in the writer's real voice — one per person, or one to all, their choice — built from true, specific memories and feelings, not generic sentiment
- A story harvest: the specific moments, sayings, and lessons surfaced in the interview, usable in the letter and beyond
- The hard-but-healing inclusions where wanted: the apology, the permission to grieve and then live, the blessing on choices the writer won't be there for
- A light plan for when/how it's read (with the will, on a date, given now) — and the note that it can be revised anytime; this is a living document, not a final one
Required Inputs
Ask for (if not already provided):
- Who it's for (each person, or everyone) and roughly how old they are / will be when they read it
- What prompted it (illness, aging, a new baby, deployment, or simply wanting to) — gently, and only as much as they offer
- The raw material: a few real memories, a value they want to pass on, something they're proud of or sorry for, what they'd say if they had one more conversation
- Voice sample: how they actually talk (paste a message, or just answer the interview naturally — the skill mirrors their cadence)
Framework
- Interview for the specific, not the summary. "I love you and I'm proud of you" is true and forgettable; "the way you refused to quit that ridiculous science project at 2am — that stubbornness is going to carry you" is unforgettable. The skill draws out concrete moments, exact sayings, the small true things. Specificity is what makes a reader feel seen years later.
- Write in their voice, not a greeting card. Mirror the writer's real cadence, including their humor, their bluntness, their particular words. A legacy letter that sounds like a template comforts no one; one that sounds like the person is like hearing them again. No inflated funeral-prose — earned warmth only.
- Include the hard things, if they want to. The most healing letters often hold an apology, a permission ("please don't stay sad — go live"), or a blessing on a future the writer won't see (marry them, take the job, be happy). The skill offers these gently and never forces them; it also never invents feelings the writer didn't express.
- Match the letter to the reader's age and moment. A letter a child reads at 8 differs from the one they read at 30. If it's for a future moment, the skill can help write to who they'll be, or suggest a short set the writer adds to over time.
- Plan the finding, keep it living. A letter no one finds is a tragedy on top of a tragedy. Light plan: where it's kept (with the will, told to a trusted person, or given directly), when it's meant to be read, and the standing invitation to revise it — people write these and live years more; it should grow with them.
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 · 108 lines · 136 tokens per session scan A 212c0b9d348c
legacy-letter is a cursor rule published in the GitHub repository mohitagw15856/pm-claude-skills (1,352 stars, last pushed 3d ago), licensed MIT. It adds 136 tokens to every session and 1,443 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-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.