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
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skillsnpx agentmods add rules/mohitagw15856/pm-claude-skills/outcome-trackerWrote 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/outcome-tracker)<a href="https://agentmods.dev/rules/mohitagw15856/pm-claude-skills/outcome-tracker"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/outcome-tracker/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/outcome-tracker"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/outcome-tracker.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.00095 | $0.01374 |
| Opus 5 | $0.00048 | $0.00687 |
| Sonnet 5 | $0.00019 | $0.00275 |
| Haiku 4.5 | $0.00010 | $0.00137 |
Grade A, and why
outcome-tracker 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 7d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Outcome Tracker Skill
Every prioritisation, forecast, and launch plan makes predictions — then everyone forgets to check them. This skill closes the loop: extract the predictions at decision time, park them somewhere durable, and score them against reality on a schedule. Over time it answers the question no one can answer today: which of our frameworks actually predict outcomes?
What This Skill Produces
- At decision time: a prediction record — each claim made falsifiable, with a metric, a direction/target, a check-by date, and a stated confidence
- At review time: an outcome scoring of due predictions (hit / miss / partial / unresolvable), with what was learned
- On demand: a calibration report — per-framework and per-confidence-band hit rates from the accumulated records
Required Inputs
Ask for (if not already provided):
- Mode — record (new decision), review (score due predictions), or calibrate (analyse the history)
- Record mode: the decision artifact (RICE table, forecast, launch plan, OKR set) and where records live (a
predictions/folder in the Brain, or a JSON/markdown file in the repo) - Review mode: the stored predictions plus current metric values for the due ones
- Calibrate mode: the prediction history (the calculator below reads it as JSON)
Making Claims Falsifiable (record mode)
Walk the artifact and force each implicit claim into this shape — a prediction that can't fill the row doesn't get recorded, it gets flagged as untestable:
| Field | Rule |
|---|---|
claim |
One sentence, future tense, about a measurable effect ("onboarding redesign lifts activation") |
metric |
The exact instrumented metric, with today's baseline |
predicted |
Direction + magnitude band ("+10-20% relative") — bands beat point estimates |
confidence |
0.5–0.95, from the author, recorded before the outcome is knowable |
check_by |
The date the effect should be visible if real; also the review trigger |
framework |
What produced the claim (rice-prioritisation, gut call, sales-forecasting-model…) — this is what calibration is about |
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.
- 7d ago First seen · 90 lines · 95 tokens per session scan A ead818aca2df
outcome-tracker is a cursor rule published in the GitHub repository mohitagw15856/pm-claude-skills (1,352 stars, last pushed 3d ago), licensed MIT. It adds 95 tokens to every session and 1,374 once invoked, about $0.0005 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.