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/networking-outreach)<a href="https://agentmods.dev/rules/mohitagw15856/pm-claude-skills/networking-outreach"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/networking-outreach/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/networking-outreach"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/networking-outreach.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.00120 | $0.00990 |
| Opus 5 | $0.00060 | $0.00495 |
| Sonnet 5 | $0.00024 | $0.00198 |
| Haiku 4.5 | $0.00012 | $0.00099 |
Grade A, and why
networking-outreach 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Networking Outreach
Most networking messages get ignored because they're generic, all about the sender, and ask for too much ("can I pick your brain?"). The ones that work are specific, respectful of the person's time, and easy to say yes to. This writes outreach tuned to who you're contacting and what you actually want — reconnecting, a referral, advice, or a cold intro — so you get replies, not silence.
What This Skill Produces
- A tuned message — matched to the relationship (old colleague, cold contact, recruiter, someone at a target company) and your actual goal
- A specific, genuine hook — a real reason you're reaching out to them (shared connection, their work, a specific interest), not a mass template
- A low-friction ask — a request that's easy and quick to grant (a specific question, a 15-minute call, a pointer) rather than an open-ended time sink
- Follow-up guidance — how and when to follow up once without being annoying
- A give-value angle — how to offer something or at least make it effortless, so it's not purely extractive
Required Inputs
Ask for these if not provided:
- The goal — reconnect, referral, advice, informational chat, job lead, or intro
- The person — who they are and your relationship (or none) with them
- The connection — anything shared (a mutual contact, their work, a common background)
- The channel — LinkedIn, email, or a warm intro
- Your context — enough that the hook is genuine (job search, career interest, etc.)
Framework: Specific, Easy, Respectful
- Make it about them and specific. Open with a genuine, particular reason you're contacting this person — their work, a shared connection, a real interest. Generic = ignored.
- Get to a clear, small ask. Say what you'd like plainly, and make it low-friction — one specific question or a short call, not "pick your brain" open-endedly.
- Respect their time. Keep it short, acknowledge they're busy, and make saying yes (or a quick pointer) easy.
- Offer or ease, don't just extract. Where you can, offer something or at least frame it so it costs them little — reciprocity, even small, changes the response.
- Follow up once, gracefully. A single, polite follow-up after a reasonable gap is fine; more isn't.
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 · 68 lines · 120 tokens per session scan A 66ae9c47d8e5
networking-outreach is a cursor rule published in the GitHub repository mohitagw15856/pm-claude-skills (1,352 stars, last pushed 3d ago), licensed MIT. It adds 120 tokens to every session and 990 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.