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/strategy-memo)<a href="https://agentmods.dev/rules/mohitagw15856/pm-claude-skills/strategy-memo"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/strategy-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/strategy-memo"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/strategy-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.00088 | $0.00793 |
| Opus 5 | $0.00044 | $0.00396 |
| Sonnet 5 | $0.00018 | $0.00159 |
| Haiku 4.5 | $0.00009 | $0.00079 |
Grade A, and why
strategy-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 8d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Strategy Memo Skill
Strategy is choosing what not to do. A real strategy memo makes a bet and names the sacrifices; a fake one is a list of goals everyone already agreed with. This skill follows the diagnosis → guiding policy → coherent actions structure, forces explicit non-goals, and ties the bet to leading indicators — so the team is aligned on a direction sharp enough to be wrong.
Required Inputs
Ask for these only if they aren't already provided:
- The strategic question — the choice or challenge this memo resolves.
- The situation — the honest diagnosis: the market, the competition, your real position and constraints.
- The bet — the approach you're choosing and what it's betting on being true.
- The trade-offs — what you'll deliberately not do or de-prioritise to make the bet.
Output Format
Strategy Memo: [the strategic question]
1. The question — the strategic choice being made, in one sentence.
2. Diagnosis — the honest read of the situation: what's really going on, the few factors that matter most, and your true position (not the aspirational one). A strategy built on a flattering diagnosis fails.
3. The bet (guiding policy) — the chosen approach and, explicitly, what it assumes is true. This is the spine — everything else serves it.
4. Why now — why this is the right bet at this moment (the window, the catalyst), not last year or next.
5. What we're NOT doing — the explicit non-goals and de-prioritisations. If this list is empty, it isn't a strategy — it's a wish list.
6. Coherent actions — the few moves that follow from the bet and reinforce each other (not a laundry list of everything).
7. How we'll know — the leading indicators that tell you the bet is working (or not) early, and the conditions under which you'd reconsider.
8. Risks — what could make the bet wrong, and which assumptions to validate first.
Quality Checks
- The diagnosis is honest about the real position, not aspirational
- The bet states what it assumes to be true — it's falsifiable
- There's an explicit "what we're NOT doing" list with real sacrifices
- The actions are few and coherent (mutually reinforcing), not an everything-list
- Leading indicators are named so you learn early whether it's working
- "Why now" is answered — the timing is justified
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.
- 8d ago First seen · 63 lines · 88 tokens per session scan A 1edfd82d16fb
strategy-memo is a cursor rule published in the GitHub repository mohitagw15856/pm-claude-skills (1,352 stars, last pushed 3d ago), licensed MIT. It adds 88 tokens to every session and 793 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.