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/bookkeeping-categorization)<a href="https://agentmods.dev/rules/mohitagw15856/pm-claude-skills/bookkeeping-categorization"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/bookkeeping-categorization/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/bookkeeping-categorization"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/bookkeeping-categorization.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.00085 | $0.00922 |
| Opus 5 | $0.00043 | $0.00461 |
| Sonnet 5 | $0.00017 | $0.00184 |
| Haiku 4.5 | $0.00009 | $0.00092 |
Grade A, and why
bookkeeping-categorization 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 9d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bookkeeping Categorization Skill
Messy books come from inconsistent categorization — the same expense landing in three different buckets. This skill sets up a sensible chart of accounts for the business and clear rules for where each kind of transaction goes (with the tricky cases called out), so the books stay clean, comparable month to month, and easy for an accountant to work from.
Note: this is an organizational aid, not tax or accounting advice. The correct treatment of specific expenses (deductibility, capitalization vs. expense, tax categories) depends on jurisdiction and your situation — confirm categories and tax handling with a qualified accountant. Never assert tax deductibility.
Working from a brief
Given "help me categorize my freelance business expenses", produce a usable chart of accounts and rules anyway — infer the relevant categories for that business type and give examples, marking anything tax-sensitive (confirm with your accountant). Never state what's tax-deductible as fact.
Required Inputs
Ask for these only if they aren't already provided (else infer and label):
- The business — type (freelance, agency, SaaS, retail…), size, and accounting basis (cash/accrual) if known.
- The tool — QuickBooks, Xero, a spreadsheet, etc. (so categories map to it).
- Typical transactions — the kinds of income and expenses that recur, and any that are confusing.
- Goal — clean monthly books, tax prep readiness, or clearer reporting.
Output Format
Bookkeeping Setup: [business]
1. Chart of accounts — a practical category list grouped by type:
- Income (sales/services, other income), COGS / direct costs, Operating expenses (the recurring categories for this business — software, contractors, marketing, rent, travel, etc.), Owner/Equity, and Other (taxes, fees).
| Category | Type | What goes here | Examples |
|---|
2. Categorization rules — clear "if it's X, it goes in Y" rules, including the edge cases that cause inconsistency:
- mixed personal/business, software vs. equipment, contractor vs. payroll, meals vs. entertainment, a refund, a transfer (not income), owner's draw (not an expense), etc. — each flagged (confirm tax treatment with your accountant) where relevant.
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.
- 9d ago First seen · 70 lines · 85 tokens per session scan A eacd443cd2bc
bookkeeping-categorization is a cursor rule published in the GitHub repository mohitagw15856/pm-claude-skills (1,357 stars, last pushed today), licensed MIT. It adds 85 tokens to every session and 922 once invoked, about $0.0004 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
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.