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 invoice-generatorgit 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/invoice-generator)<a href="https://agentmods.dev/skills/mohitagw15856/pm-claude-skills/invoice-generator"><img src="https://agentmods.dev/badge/skills/mohitagw15856/pm-claude-skills/invoice-generator/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/invoice-generator"><img src="https://agentmods.dev/badge/skills/mohitagw15856/pm-claude-skills/invoice-generator.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.00093 | $0.00936 |
| Opus 5.5 | $0.00037 | $0.00374 |
| Sonnet 5.5 | $0.00019 | $0.00187 |
| Haiku 4.5 | $0.00009 | $0.00094 |
Grade A, and why
invoice-generator 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Invoice Generator Skill
An invoice that's clear and complete gets paid faster — it has the details a client (and their finance team) need to approve and pay without a back-and-forth. This skill produces a professional invoice with everything in the right place: itemised work, the totals, and how and when to pay.
Note: this is a documentation aid, not tax, accounting, or legal advice. Tax handling (VAT/GST/sales tax, reverse charge, withholding), required fields, and registration numbers vary by country and situation — confirm your tax treatment and legal requirements with an accountant. Tax lines below are flagged to set.
Working from a brief
Given "invoice a client $2,000 for a website project", produce the full invoice anyway — lay out every standard field and mark the ones to set (your detail) (invoice number, dates, tax rate, payment details). Compute the arithmetic from the line items you're given; don't invent a tax rate — flag it to set.
Required Inputs
Ask for these only if they aren't already provided (else mark to set):
- From / to — your business name + contact (and tax/registration ID if applicable), and the client's billing details.
- Line items — description of work/goods, quantity, unit rate.
- Tax — whether tax applies and the rate (flag to confirm), or exempt/not applicable.
- Terms — payment due (e.g. Net 30), accepted methods (bank transfer, card, etc.), and any late-payment terms.
- References — PO number, project name, invoice number (or note your numbering scheme).
Output Format
Invoice
- Header — "INVOICE", a unique invoice number, issue date, and due date.
- From — your business name, address, contact, tax/registration ID (if any).
- Bill to — client name, address, contact; PO/reference if provided.
- Line items — a table: description · qty · unit rate · amount.
| Description | Qty | Rate | Amount |
|---|
- Totals — subtotal, tax (rate + amount, flag to set), discounts if any, and total due (in the right currency). Show the arithmetic so it's verifiable.
- Payment details — how to pay (bank/account details, payment link, etc.) and the terms (due date, late fee if any).
- Notes — a short thank-you / any terms; and a reminder to confirm tax treatment with an accountant.
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 · 75 lines · 93 tokens per session scan A 06100b0556d5
invoice-generator is a skill published in the GitHub repository mohitagw15856/pm-claude-skills (1,449 stars, last pushed today), licensed MIT. It adds 93 tokens to every session and 936 once invoked, about $0.0004 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…