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/financial-statement-explainer)<a href="https://agentmods.dev/rules/mohitagw15856/pm-claude-skills/financial-statement-explainer"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/financial-statement-explainer/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/financial-statement-explainer"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/financial-statement-explainer.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.00100 | $0.00933 |
| Opus 5 | $0.00050 | $0.00466 |
| Sonnet 5 | $0.00020 | $0.00187 |
| Haiku 4.5 | $0.00010 | $0.00093 |
Grade A, and why
financial-statement-explainer 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 6d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Financial Statement Explainer Skill
Financial statements are precise but opaque to most people. This skill translates a P&L, balance sheet, or cash flow into plain English — what each part means, which numbers actually matter, and the story they tell about the business — so a founder, manager, or operator can read their own financials and make decisions.
Note: this is an educational explainer, not financial, investment, tax, or accounting advice. It explains figures the user provides; it does not audit them or recommend financial decisions. Verify numbers and any decisions with a qualified accountant/advisor. Never invent figures.
Working from a brief
Given a statement (or a few key numbers), explain it anyway — walk through the structure and interpret the figures provided. Where a number isn't given, explain what to look for rather than inventing it. Never fabricate amounts or compute ratios from numbers you weren't given.
Required Inputs
Ask for these only if they aren't already provided (else explain generally / mark unknown):
- The statement — which one (P&L / balance sheet / cash flow), the figures, and the period.
- The reader — who needs to understand it and why (a founder, a manager, an investor conversation).
- The question behind it — what they're trying to learn (Are we profitable? Can we make payroll? Why is cash tight?).
- Context — business type/stage, if it helps interpret what's normal.
Output Format
[Statement] Explained
- What this statement tells you — one or two lines on what this statement is for (P&L = profitability over a period; balance sheet = what you own/owe at a point; cash flow = where cash actually moved).
- Section-by-section — walk the structure in plain terms, using the provided numbers:
- P&L: revenue → COGS → gross profit/margin → operating expenses → operating income → net income; what each step means.
- Balance sheet: assets, liabilities, equity; the accounting equation; what current vs. long-term means.
- Cash flow: operating, investing, financing; why profit ≠ cash.
- The numbers that matter — the few line items and ratios worth watching for this reader (e.g. gross margin, burn, current ratio, runway) — with the formula and the figure if the inputs were given.
- The story — what the statement is saying overall (healthy/strained, improving/declining, where to look).
- Watch-outs & next questions — what looks notable and what to ask 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.
- 6d ago First seen · 65 lines · 100 tokens per session scan A a58bc76c48d8
financial-statement-explainer is a cursor rule published in the GitHub repository mohitagw15856/pm-claude-skills (1,345 stars, last pushed yesterday), licensed MIT. It adds 100 tokens to every session and 933 once invoked, about $0.0005 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-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.