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/career-pivot-plan)<a href="https://agentmods.dev/rules/mohitagw15856/pm-claude-skills/career-pivot-plan"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/career-pivot-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/career-pivot-plan"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/career-pivot-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.00117 | $0.01067 |
| Opus 5 | $0.00059 | $0.00534 |
| Sonnet 5 | $0.00023 | $0.00213 |
| Haiku 4.5 | $0.00012 | $0.00107 |
Grade A, and why
career-pivot-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 7d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Career Pivot Plan
Career changes stall on two myths: "I have to start from scratch" and "I have to quit and figure it out." Neither is true. Most pivots are bridges — leveraging what transfers, closing specific gaps, and entering through a side door — often without a heroic income cliff. This maps your transferable strengths, the real gaps, and a staged plan that gets you there while staying solvent.
What This Skill Produces
- A transferable-skills map — what from your current background genuinely carries into the target field (usually more than you think)
- An honest gap analysis — the specific skills, credentials, or experience the target role actually requires that you lack
- A staged bridge — a sequence (learn → build proof → reposition → side-door in) rather than a single leap
- A runway reality check — the financial and timeline realities, and lower-risk paths (transitional roles, hybrid moves, moonlighting)
- A repositioning narrative — how to tell your story so your background reads as an asset, not a liability
- Concrete next steps — the first few moves to start now
Required Inputs
Ask for these if not provided:
- From → to — your current field/role and the target
- The why — what's driving the change (helps aim it)
- Your assets — skills, experience, network, and any relevant interests/projects
- Constraints — financial runway, timeline, obligations, risk tolerance
- What you've explored — any research or steps already taken
Framework: Bridge, Don't Leap
- Inventory what transfers. Most skills (communication, analysis, project work, domain knowledge) carry across — map these first to shrink the perceived gap.
- Analyze the real gap, honestly. Identify what the target role genuinely requires that you lack (skills, credential, portfolio, network) — not a vague sense of unqualified.
- Stage the bridge. Build skills and proof, reposition your story, and look for side-door entries (adjacent roles, internal moves, transitional titles) rather than a cold leap.
- Respect the runway. Be realistic about money and time; favor lower-risk paths (moonlighting, a transitional role, part-time study) over quitting into uncertainty.
- Rewrite the narrative. Frame the background as an asset the target field values, with a clear "why this makes sense" story — not an apology for a change.
- Start small now. Give the first concrete steps (a conversation, a course, a project) to build momentum.
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.
- 7d ago First seen · 74 lines · 117 tokens per session scan A b3f64836fcfe
career-pivot-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 117 tokens to every session and 1,067 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-09-03.
Other cursor rules, from other repositories
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.