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/decision-memo)<a href="https://agentmods.dev/rules/mohitagw15856/pm-claude-skills/decision-memo"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/decision-memo/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/decision-memo"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/decision-memo.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.00083 | $0.00803 |
| Opus 5 | $0.00042 | $0.00402 |
| Sonnet 5 | $0.00017 | $0.00161 |
| Haiku 4.5 | $0.00008 | $0.00080 |
Grade A, and why
decision-memo 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Decision Memo Skill
A decision memo exists to get a decision made — fast, on the record, by the right person. The failure mode is a memo that reads like a discussion: lots of context, no recommendation, no ask. This skill front-loads the recommendation and the decision being requested, then supports it — so the reader can say yes, no, or "here's my concern" in five minutes.
Required Inputs
Ask for these only if they aren't already provided:
- The decision — the specific choice to be made (phrase it as a question with a yes/no or A/B/C answer).
- The recommendation — your actual recommendation (a memo without one is a status update).
- The options considered and their trade-offs.
- The decider & deadline — who owns this call and by when.
Output Format
Decision Memo: [the decision]
To: [decider] · From: [you] · Date: [date] · Decision needed by: [date]
1. Recommendation (TL;DR) — the recommendation in 2–3 sentences, first. What you want them to approve, and the one-line why.
2. The decision — the question being decided, framed so the answer is a clear choice.
3. Context — the minimum background needed to evaluate it (link the rest). Why this is on the table now.
4. Options & trade-offs — a table; be fair to the options you're not recommending (a stacked deck reads as one):
| Option | Pros | Cons | Cost / effort |
|---|
5. Why this recommendation — the reasoning, and what you'd have to believe for it to be wrong (the assumptions it rests on).
6. Risks & mitigations — the real downsides and how you'd handle them. A reversible decision deserves less agonising than an irreversible one — say which it is.
7. The ask — exactly what you need from the reader: approve / pick an option / give input — by the deadline.
Quality Checks
- The recommendation is in the first paragraph, not the conclusion
- The decision is framed as a clear question with a finite set of answers
- Options not recommended are presented fairly, with real pros
- The memo states what would have to be true for the recommendation to be wrong
- It says whether the decision is reversible (one-way vs. two-way door)
- There is an explicit ask and a decision deadline
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 · 65 lines · 83 tokens per session scan A 79ddacc3507a
decision-memo is a cursor rule published in the GitHub repository mohitagw15856/pm-claude-skills (1,357 stars, last pushed yesterday), licensed MIT. It adds 83 tokens to every session and 803 once invoked, about $0.0004 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.