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.
npx skills add mohitagw15856/pm-claude-skills --skill decision-memogit 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/skills/mohitagw15856/pm-claude-skills/decision-memo)<a href="https://agentmods.dev/skills/mohitagw15856/pm-claude-skills/decision-memo"><img src="https://agentmods.dev/badge/skills/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/skills/mohitagw15856/pm-claude-skills/decision-memo"><img src="https://agentmods.dev/badge/skills/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.00087 | $0.00873 |
| Opus 5.5 | $0.00035 | $0.00349 |
| Sonnet 5.5 | $0.00017 | $0.00175 |
| Haiku 4.5 | $0.00009 | $0.00087 |
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 2d 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 — 73 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.
Not quite this? Use
async-decision-memowhen the decision will be made asynchronously, with a read window, comments and a deadline.
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
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.
- 2d ago First seen · 73 lines · 87 tokens per session scan A 798d79065c47
decision-memo is a skill published in the GitHub repository mohitagw15856/pm-claude-skills (1,449 stars, last pushed today), licensed MIT. It adds 87 tokens to every session and 873 once invoked, about $0.0003 per session on Opus 5.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-10-12.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…