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/board-pre-read)<a href="https://agentmods.dev/rules/mohitagw15856/pm-claude-skills/board-pre-read"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/board-pre-read/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/board-pre-read"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/board-pre-read.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.00087 | $0.00807 |
| Opus 5 | $0.00044 | $0.00404 |
| Sonnet 5 | $0.00017 | $0.00161 |
| Haiku 4.5 | $0.00009 | $0.00081 |
Grade A, and why
board-pre-read 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Board Pre-Read Skill
The best board meetings spend zero time on status because the board already read it. A pre-read sent 48+ hours ahead does that: it conveys the state of the business and, crucially, tells the board exactly what input and decisions are needed — so the meeting is discussion and decisions, not a slide-reading session. This skill structures that document.
Required Inputs
Ask for these only if they aren't already provided:
- The headline — the one thing the board should take away this period (good or bad).
- Metrics vs. plan — the key numbers against the plan/forecast (revenue, growth, burn, runway, the north-star).
- What changed — major wins, misses, and shifts since last meeting.
- Decisions/asks — what you actually need from the board (approval, input, introductions).
Output Format
Board Pre-Read — [company], [month/quarter]
Sent: [date, ≥48h before the meeting]
1. TL;DR — 3–5 bullets: the state of the business, the headline, runway, and the decisions you're bringing. A busy board member should get the gist from this alone.
2. Metrics dashboard — the core numbers vs. plan, with the trend and a one-line "so what" each. Show misses honestly — boards trust founders who surface bad news first.
| Metric | This period | vs. plan | Trend | Note |
|---|
3. What's working — the 2–3 things going well and why (so they can be doubled down on).
4. What's not — the 2–3 problems, what you're doing about them, and where you want the board's help. Candour here is the whole game.
5. Decisions & asks — explicit: "We're asking the board to approve X" / "We'd value input on Y" / "We need intros to Z." Tie each to the agenda.
6. Risks & watch-items — the top risks to the plan and runway, and the leading indicators you're watching.
Appendix — detail, financials, and supporting data (linked, not inline).
Quality Checks
- It's genuinely a pre-read — sent ahead, readable without a presenter
- The TL;DR stands alone for a time-pressed director
- Metrics are shown vs. plan, with misses surfaced honestly (not buried)
- The decisions/asks for the board are explicit and tied to the agenda
- Runway and the top risks are stated plainly
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 · 64 lines · 87 tokens per session scan A 23f4fb14e1aa
board-pre-read is a cursor rule published in the GitHub repository mohitagw15856/pm-claude-skills (1,357 stars, last pushed yesterday), licensed MIT. It adds 87 tokens to every session and 807 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.