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/first-hire-plan)<a href="https://agentmods.dev/rules/mohitagw15856/pm-claude-skills/first-hire-plan"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/first-hire-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/first-hire-plan"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/first-hire-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.00133 | $0.01106 |
| Opus 5 | $0.00067 | $0.00553 |
| Sonnet 5 | $0.00027 | $0.00221 |
| Haiku 4.5 | $0.00013 | $0.00111 |
Grade A, and why
first-hire-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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
First-Hire Plan
Your first hire is a big, nervy step — get the role wrong or the classification wrong and it's costly. This helps you decide whether you're ready, what to hand off first, and whether a contractor or employee fits — then gives a simple, fair hiring process for someone who's never done it, plus the obligations to know about. It flags that employment, tax, and legal rules are local and this isn't legal advice.
What This Skill Produces
- A readiness & role read — whether now's the time, and which work to offload first (the highest-leverage or most-draining tasks)
- Contractor vs. employee — the trade-offs for your situation (cost, control, commitment, classification rules) and a recommendation
- A lightweight hiring process — defining the role, sourcing candidates, a fair and simple evaluation, and making an offer
- Obligations awareness — the tax, payroll, insurance, and legal responsibilities a first hire triggers (flagged to verify locally)
- Onboarding basics — setting the person up to succeed in the first weeks
- A boundary — employment/tax/legal specifics are local; consult a professional
Required Inputs
Ask for these if not provided:
- The business — what you do, size, and where you're stretched
- The need — what work you'd hand off, and how much of it
- Budget & commitment — what you can afford, and how steady the need is
- Contractor or employee leaning — any preference or constraint
- Location — for the (varying) employment/tax obligations
Framework: Right Time, Right Role, Right Classification
- Check readiness and pick the role. Confirm the workload and budget justify a hire, then define the highest-leverage thing to hand off first — don't hire a vague "help."
- Decide contractor vs. employee honestly. Weigh cost, control, commitment, and — critically — classification rules (misclassifying an employee as a contractor is a real risk). Recommend the fit.
- Define the role clearly. A concrete role description (responsibilities, must-haves, success in 90 days) makes sourcing and evaluation fair and effective.
- Run a simple, fair process. Source candidates, evaluate on relevant signals (a small work sample beats gut feel), and make a clear offer.
- Know the obligations. A first hire can trigger payroll, tax withholding, insurance, and legal duties — flag these to set up correctly, verified locally.
- Onboard deliberately. Set expectations, tools, and early wins so the hire actually reduces your load.
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 · 71 lines · 133 tokens per session scan A c73f0b4a1117
first-hire-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 133 tokens to every session and 1,106 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-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.