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 cash-flow-forecastgit 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/cash-flow-forecast)<a href="https://agentmods.dev/skills/mohitagw15856/pm-claude-skills/cash-flow-forecast"><img src="https://agentmods.dev/badge/skills/mohitagw15856/pm-claude-skills/cash-flow-forecast/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/cash-flow-forecast"><img src="https://agentmods.dev/badge/skills/mohitagw15856/pm-claude-skills/cash-flow-forecast.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.00104 | $0.00987 |
| Opus 5.5 | $0.00042 | $0.00395 |
| Sonnet 5.5 | $0.00021 | $0.00197 |
| Haiku 4.5 | $0.00010 | $0.00099 |
Grade A, and why
cash-flow-forecast 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cash Flow Forecast Skill
Profit is an opinion; cash is a fact — and businesses fail by running out of it even while "profitable". A short-term (commonly 13-week) cash flow forecast shows, week by week, whether money coming in covers money going out, and when the tightest point hits. This skill builds that forecast's structure and math so you can see trouble early and act.
Note: this is a planning aid, not financial, investment, or accounting advice. It structures a forecast from figures you provide and projects from your assumptions; it does not guarantee outcomes. Confirm material decisions with a qualified accountant/advisor. Never invent actual balances or amounts.
Working from a brief
Given "build me a 13-week cash flow", produce the full structure anyway — lay out the model with the formulas and a worked example using placeholder figures (replace with your numbers). Use the real numbers where the user gave them; never fabricate a starting balance or a result.
Required Inputs
Ask for these only if they aren't already provided (else use labelled placeholders):
- Starting cash — current bank balance (the opening position).
- Inflows — expected receipts and their timing (customer payments, with realistic collection timing, not invoice date).
- Outflows — scheduled payments and timing (payroll, rent, suppliers, loan repayments, tax, subscriptions).
- Horizon & purpose — 13 weeks (default) or other, and what decision it informs (a crunch, a hire, a raise).
Output Format
13-Week Cash Flow Forecast: [business]
- How it works — the model in one line:
Closing cash = Opening cash + Inflows − Outflows, run week over week (each week's closing is the next week's opening). - Forecast table — a week-by-week layout (template + a worked example with placeholder figures):
| Week | Opening cash | Inflows | Outflows | Net | Closing cash |
|---|
Break inflows/outflows into their main lines (receipts; payroll, rent, suppliers, tax…) so it's actionable.
- Key read-outs — the lowest cash point and which week it hits, weeks that go negative (the warning), and total net movement over the horizon.
- Assumptions — collection timing, what's committed vs. expected, and anything to confirm — stated explicitly (the forecast is only as good as these).
- If cash goes tight — levers — accelerate receivables, delay/stagger payables, cut/defer discretionary spend, draw on credit, or raise — with the trade-offs.
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 · 76 lines · 104 tokens per session scan A 542e4fa194f1
cash-flow-forecast is a skill published in the GitHub repository mohitagw15856/pm-claude-skills (1,449 stars, last pushed today), licensed MIT. It adds 104 tokens to every session and 987 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…