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/reconnect-with-someone)<a href="https://agentmods.dev/rules/mohitagw15856/pm-claude-skills/reconnect-with-someone"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/reconnect-with-someone/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/reconnect-with-someone"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/reconnect-with-someone.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.00140 | $0.01104 |
| Opus 5 | $0.00070 | $0.00552 |
| Sonnet 5 | $0.00028 | $0.00221 |
| Haiku 4.5 | $0.00014 | $0.00110 |
Grade A, and why
reconnect-with-someone 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 12d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reconnect With Someone
Most lost friendships didn't end — they just drifted, and then the gap itself became the barrier ("it's been so long, it'd be weird now"). But the other person almost always feels the same and is glad you reached out. This gets you past the awkwardness with a warm message that acknowledges the gap lightly, gives a genuine reason for reaching out, and reopens the door — because reconnecting usually just needs one person brave enough to text first.
What This Skill Produces
- The awkwardness reframe — why the gap feels bigger to you than to them, and why they'll likely be glad, not annoyed
- A warm reach-out message — one that acknowledges the time lightly (not a groveling apology) and feels genuine
- A specific hook — the reason for reaching out now (a shared memory, something that reminded you of them, a life update, or simply "you crossed my mind")
- The path forward — how to move from the reopening message toward actually reconnecting (a call, a meet-up) without overloading the first message
- A no-pressure stance — how to reach out warmly without making them feel guilty for the drift either
Required Inputs
Ask for these if not provided:
- Who — the person and your history (close friend, old colleague, relative)
- The gap — how long, and roughly why you drifted (moved, life, a small falling-out)
- What prompted it — why you want to reconnect now
- Any complication — was there tension, or did it just fade
Framework: Acknowledge Lightly, Give A Hook, Reopen
- Shrink the awkwardness. Remind the person that the other side almost certainly feels the gap too and will be glad — the barrier is mostly in their own head.
- Acknowledge the time, lightly. A brief, warm nod to the gap ("I know it's been ages!") beats either ignoring it or a heavy apology that makes it awkward.
- Give a genuine hook. A specific reason lands better than a bare "hey" — a memory, something that reminded you of them, a life update, or an honest "you popped into my head and I miss you."
- Keep the first message light. Reopen the door — don't cram a friendship's worth of catching-up or a big ask into the first text.
- Move toward real reconnection. Once they reply, suggest a low-key call or meet-up — the message is the door, the conversation is the room.
- No guilt, either way. Reach out warmly without blaming them (or yourself) for the drift — keep it light and forward-looking.
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.
- 12d ago First seen · 69 lines · 140 tokens per session scan A 7745f78af4bb
reconnect-with-someone is a cursor rule published in the GitHub repository mohitagw15856/pm-claude-skills (1,357 stars, last pushed today), licensed MIT. It adds 140 tokens to every session and 1,104 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-08-30.
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.