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/new-manager-first-90-days)<a href="https://agentmods.dev/rules/mohitagw15856/pm-claude-skills/new-manager-first-90-days"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/new-manager-first-90-days/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/new-manager-first-90-days"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/new-manager-first-90-days.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.00125 | $0.01177 |
| Opus 5 | $0.00063 | $0.00589 |
| Sonnet 5 | $0.00025 | $0.00235 |
| Haiku 4.5 | $0.00013 | $0.00118 |
Grade A, and why
new-manager-first-90-days 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
New Manager: First 90 Days
The jump to managing is a role change, not a promotion for doing more of the same — and most first-time managers stumble by either changing everything on day one or staying an individual contributor with a title. This gives a phased first-90-days plan: earn trust and learn first, then set direction, then adjust — plus how to handle the 1:1s, delegation, and hard conversations that define the job.
What This Skill Produces
- A phased 90-day plan — listen & learn (first weeks) → set direction (mid) → adjust & build (later), instead of changing everything at once
- First 1:1s — how to run them to build trust and understand each person (their goals, working style, and what they need from you)
- The mindset shift — moving from doer to enabler: your output is now the team's output
- Trap avoidance — the classic first-time mistakes (doing the work yourself, changing too fast, avoiding difficult conversations, playing favorites)
- Early wins — credibility-building moves that help the team without overstepping
- A read on the situation — inheriting a team vs. building one, peers-now-reports, or a struggling team
Required Inputs
Ask for these if not provided:
- The situation — inherited team, new team, promoted over former peers, or a turnaround
- The team — size, and what you know about how it's doing
- Your background — first-time manager or experienced, and your relationship to the team
- The context — org expectations, any pressing issues
- Your worry — what you're most unsure about
Framework: Learn, Then Lead
- Listen before you change. Spend the early weeks understanding the team, the work, and the context before making changes — early sweeping changes without understanding destroy trust.
- Invest in 1:1s. Use first 1:1s to learn each person's goals, strengths, working style, and needs — relationships are the foundation of everything else.
- Make the mindset shift. Your job is now to enable the team, not to be the top individual contributor — resist doing the work yourself; delegate and develop.
- Set direction once you understand. After learning, clarify priorities, expectations, and how the team will work — then adjust based on what you see.
- Don't dodge the hard stuff. Address underperformance and tensions kindly but directly; avoiding difficult conversations early is a trap that compounds.
- Bank early, appropriate wins. Small improvements and removing blockers build credibility without overstepping your still-forming understanding.
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 · 72 lines · 125 tokens per session scan A 575656045abd
new-manager-first-90-days is a cursor rule published in the GitHub repository mohitagw15856/pm-claude-skills (1,357 stars, last pushed yesterday), licensed MIT. It adds 125 tokens to every session and 1,177 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
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.