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.
npx skills add mohitagw15856/pm-claude-skills --skill collections-emailgit 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/skills/mohitagw15856/pm-claude-skills/collections-email)<a href="https://agentmods.dev/skills/mohitagw15856/pm-claude-skills/collections-email"><img src="https://agentmods.dev/badge/skills/mohitagw15856/pm-claude-skills/collections-email/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/skills/mohitagw15856/pm-claude-skills/collections-email"><img src="https://agentmods.dev/badge/skills/mohitagw15856/pm-claude-skills/collections-email.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.00084 | $0.00963 |
| Opus 5.5 | $0.00034 | $0.00385 |
| Sonnet 5.5 | $0.00017 | $0.00193 |
| Haiku 4.5 | $0.00008 | $0.00096 |
Grade A, and why
collections-email 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 2d 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.
Collections Email Skill
Chasing payment is uncomfortable, so it's often done too late or too harshly. The effective approach is a staged sequence that starts friendly and firms up on a schedule — always professional, always making it trivially easy to pay. This skill writes that sequence so you get paid without burning the relationship.
Note: this is a communication aid, not legal or debt-collection advice. Late-payment interest, statutory rights, and regulated debt-collection rules vary by jurisdiction — confirm any interest/late fees and escalation (collections agency, legal) with an accountant/lawyer before acting on them.
Working from a brief
Given "chase a client whose $5,000 invoice is 2 weeks overdue", write the full sequence anyway — infer a sensible cadence and tone progression, marking specifics (insert invoice #, amount, dates, payment link). Don't state late-fee/interest amounts as enforceable — flag them to confirm. Never threaten beyond what's lawful/intended.
Required Inputs
Ask for these only if they aren't already provided (else mark to insert):
- The invoice — number, amount, original due date, and how overdue it is.
- The relationship — client name, contact, and whether they're a valued ongoing client or a one-off.
- Terms — your payment terms and any agreed late-fee/interest (flag to confirm enforceability).
- Payment method — exactly how they can pay (link, bank details), to remove friction.
Output Format
Collections Sequence: [invoice]
A staged set of emails, each short, professional, and with a clear pay-now path:
- Pre-due reminder (optional, ~3–5 days before) — friendly heads-up the invoice is due soon.
- Due-date / just-overdue (day 0–3) — assume an oversight; warm nudge, restate amount + due date + how to pay.
- Overdue reminder (~7–14 days) — firmer, still polite; note it's now overdue, ask for a payment date or to flag an issue.
- Second overdue (~21–30 days) — clear and direct; reference the terms, request immediate payment or a call, mention any agreed late fee (confirm).
- Final notice (~30–45 days) — formal; state the next step if unpaid (pause work, escalate per terms) — factual, not threatening.
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.
- 2d ago First seen · 74 lines · 84 tokens per session scan A 26947f3aafc7
collections-email is a skill published in the GitHub repository mohitagw15856/pm-claude-skills (1,449 stars, last pushed today), licensed MIT. It adds 84 tokens to every session and 963 once invoked, about $0.0003 per session on Opus 5.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-10-12.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…