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/agent-incident-postmortem)<a href="https://agentmods.dev/rules/mohitagw15856/pm-claude-skills/agent-incident-postmortem"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/agent-incident-postmortem/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/agent-incident-postmortem"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/agent-incident-postmortem.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.00113 | $0.01230 |
| Opus 5 | $0.00056 | $0.00615 |
| Sonnet 5 | $0.00023 | $0.00246 |
| Haiku 4.5 | $0.00011 | $0.00123 |
Grade A, and why
agent-incident-postmortem 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Incident Postmortem Skill
AI incidents differ from outages: the system didn't go down — it did something wrong, confidently, and maybe only once. This skill adapts blameless postmortem practice to nondeterministic systems, where "can we reproduce it?" needs traces, not just steps.
What This Skill Produces
- A blameless postmortem document with timeline and user/business impact
- A trace reconstruction of what the agent saw, decided, and did
- A root-cause analysis across the AI failure layers (not "the model hallucinated" as a conclusion)
- Corrective actions — always including a new permanent case in the regression suite
Required Inputs
Ask for (if not already provided):
- What the agent did and what it should have done
- The trace — the full request: system prompt, context, tool calls and results, output. If no trace exists, that absence is itself a finding
- Blast radius — how many users/requests, over what window, and whether it's ongoing
- Detection — how it was noticed (user report? monitor? luck?) and how long after it started
Root-Cause Layers
Walk the layers in order; the root cause is usually the earliest layer that could have prevented the outcome. "The model was wrong" is a starting point, never the conclusion — models are known to be fallible, so the question is what let a fallible output become an incident.
| Layer | Ask |
|---|---|
| Input / context | Was the context wrong, stale, contradictory, or poisoned (injection)? Did retrieval feed it bad ground truth? |
| Model behaviour | Given that context, was the output a foreseeable failure mode (fabrication under missing data, over-compliance with injected text)? |
| Guardrails | What check should have caught this output and didn't exist / didn't fire? (schema validation, groundedness check, action allow-list) |
| Action layer | Why could the wrong output become a real action or reach a user without the appropriate gate for its risk level? |
| Detection | Why did we learn about it this way, this late? What signal would have caught it in minutes? |
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 · 92 lines · 113 tokens per session scan A 31463f825254
agent-incident-postmortem is a cursor rule published in the GitHub repository mohitagw15856/pm-claude-skills (1,345 stars, last pushed 2d ago), licensed MIT. It adds 113 tokens to every session and 1,230 once invoked, about $0.0006 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.