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/used-car-decoder)<a href="https://agentmods.dev/rules/mohitagw15856/pm-claude-skills/used-car-decoder"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/used-car-decoder/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/used-car-decoder"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/used-car-decoder.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.00129 | $0.01605 |
| Opus 5 | $0.00064 | $0.00803 |
| Sonnet 5 | $0.00026 | $0.00321 |
| Haiku 4.5 | $0.00013 | $0.00161 |
Grade A, and why
used-car-decoder 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 10d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Used Car Decoder Skill
A used-car listing is a document written by someone who knows the car's problems, for someone who doesn't. The dialect is learnable: "selling for a friend" (distance from liability), "drives well for its age" (adjusted expectations), "minor cosmetic damage" (photographed from the good side), "no test drives without deposit" (walk away now). This skill decodes the ad the way [[lease-decoder]] reads a lease — severity-ranked, money math attached — then arms the viewing: the checks a non-mechanic can actually do, the questions that surface evasion, and the honest boundary: which findings mean pay a professional for an inspection and which mean leave.
What This Skill Produces
- A listing decode: phrase-by-phrase, 🔴🟡🟢, with what each hedge typically means and the question that tests it
- The before-you-travel checks: history/title verification items (accident/write-off status, finance owing, mileage consistency, recalls) — each flagged as country-specific-verify-locally with what to search, since registries differ everywhere
- A viewing & test-drive checklist ordered by cost-of-miss: the cold-start, the panel-gap walk, fluids, tires including the spare-match, electronics sweep, the specific listen-fors on the drive
- Seller questions that make evasion visible ("why selling?", "what would you fix next?", "can I take it for a pre-purchase inspection?" — the last one is the real test: honest sellers say yes)
- The money frame: comps from sold prices, what each found flaw is worth in negotiation, and the walk-away list where no price is right
Required Inputs
Ask for (if not already provided):
- The listing text and photos described, plus price and the car (make/model/year/mileage)
- The buyer: first car or fifteenth, mechanical comfort level, who else might inspect with them
- Budget truth: the price ceiling including the first-year surprises buffer (insurance, immediate maintenance)
- Country — for the verify-local flags on history checks and paperwork (this skill never asserts registry procedures)
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.
- 10d ago First seen · 137 lines · 129 tokens per session scan A 3475af6fdea4
used-car-decoder is a cursor rule published in the GitHub repository mohitagw15856/pm-claude-skills (1,345 stars, last pushed 2d ago), licensed MIT. It adds 129 tokens to every session and 1,605 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-08-30.
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-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.