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-minutes)<a href="https://agentmods.dev/rules/mohitagw15856/pm-claude-skills/board-minutes"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/board-minutes/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-minutes"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/board-minutes.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.00066 | $0.01483 |
| Opus 5 | $0.00033 | $0.00741 |
| Sonnet 5 | $0.00013 | $0.00297 |
| Haiku 4.5 | $0.00007 | $0.00148 |
Grade A, and why
board-minutes 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Board Minutes Skill
Produce formal board meeting minutes that are concise, defensible, and useful as the official record. The minutes should capture what the board considered, what was decided, what actions were assigned, and any formal resolutions — without turning the document into a transcript.
What This Skill Produces
- Formal board minutes ready for review by the chair, company secretary, or governance lead
- A clear record of attendees, apologies, quorum, conflicts of interest, agenda items, decisions, resolutions, and actions
- An action register with owners, due dates, and status
- Optional draft approval wording for the next board meeting
Required Inputs
Ask for these if not already provided:
- Organisation / company name and board or committee name
- Meeting date, time, location, and meeting type (regular / special / committee)
- Attendees, apologies, guests, and chair / secretary names
- Agenda or topic list
- Meeting notes, transcript, or bullet summary of the discussion
- Decisions made, formal resolutions passed, votes, abstentions, or objections
- Actions agreed — owner and due date for each, if known
- Any conflicts of interest, confidential items, or matters to redact from circulation
Minute-Taking Principles
- Record decisions, rationale, and actions — not a verbatim transcript.
- Use neutral, factual language. Avoid attributing opinions unless attribution is necessary for a conflict, dissent, or formal record.
- Separate discussion from decisions. A reader should be able to find what was approved and who must do what next.
- Preserve exact resolution wording when the source materials provide it; formal resolutions often need verbatim treatment.
- Keep legal precision without over-lawyering. If the notes mention regulated, legal, employment, or financial matters, flag that the draft should be reviewed by the appropriate governance or legal owner.
- Do not invent quorum, votes, attendees, or resolutions. Mark unknown items as
[to confirm].
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 · 147 lines · 66 tokens per session scan A 66838ce05a09
board-minutes is a cursor rule published in the GitHub repository mohitagw15856/pm-claude-skills (1,359 stars, last pushed today), licensed MIT. It adds 66 tokens to every session and 1,483 once invoked, about $0.0003 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.