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/delta-briefing)<a href="https://agentmods.dev/rules/mohitagw15856/pm-claude-skills/delta-briefing"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/delta-briefing/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/delta-briefing"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/delta-briefing.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.00065 | $0.00956 |
| Opus 5 | $0.00032 | $0.00478 |
| Sonnet 5 | $0.00013 | $0.00191 |
| Haiku 4.5 | $0.00006 | $0.00096 |
Grade A, and why
delta-briefing 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 8d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Delta Briefing Skill
The failure mode of every recurring report is that edition 6 reads like edition 5. This skill structures a recurring brief around the delta: read the last edition's state, diff the world against it, lead with what changed, and save state for the next run.
What This Skill Produces
- A changes-first brief: new / changed / resolved / unchanged-but-watched
- A state record (compact, machine-readable) that the next edition diffs against
- An explicit "nothing changed" edition format — short, honest, and still useful
Required Inputs
Ask for (if not already provided):
- The brief's subject and audience (competitive landscape, product metrics, account health…)
- The previous edition or state record — if none exists, this run is the baseline: say so in the output and produce the first state record
- Current sources for this cycle
- Where state lives between runs (a file next to the brief, a Brain folder — see BRAIN.md if using this library's memory)
Delta Method
- Load last state. Parse the previous state record (or previous edition if that's all there is). List the items it tracked and their status.
- Re-observe. Gather this cycle's facts from the sources — independently of the old state, so removals are caught too.
- Diff into four buckets:
- New — present now, absent last time
- Changed — tracked before, materially different now (state what moved, old → new)
- Resolved / gone — tracked before, no longer present or no longer a concern
- Watching — unchanged but still worth tracking (compressed to one line each)
- Judge materiality. A delta makes the brief only if the audience would act differently knowing it. Trivia goes to the state record, not the brief.
- Write state for next time. Every tracked item, its current status, the date, and the sources read.
Output Format
[Brief name] — [date] (edition [n], previous: [date])
TL;DR: [1-2 sentences: the most consequential delta, or "no material changes"]
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.
- 8d ago First seen · 81 lines · 65 tokens per session scan A cd7a7ee08d45
delta-briefing is a cursor rule published in the GitHub repository mohitagw15856/pm-claude-skills (1,352 stars, last pushed 3d ago), licensed MIT. It adds 65 tokens to every session and 956 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
cursor
Always-on my-adhd-caveman. Off with "stop adhd-caveman" or "normal mode".
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.