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.
npx skills add mohitagw15856/pm-claude-skills --skill spot-ai-mistakesgit 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/skills/mohitagw15856/pm-claude-skills/spot-ai-mistakes)<a href="https://agentmods.dev/skills/mohitagw15856/pm-claude-skills/spot-ai-mistakes"><img src="https://agentmods.dev/badge/skills/mohitagw15856/pm-claude-skills/spot-ai-mistakes/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/skills/mohitagw15856/pm-claude-skills/spot-ai-mistakes"><img src="https://agentmods.dev/badge/skills/mohitagw15856/pm-claude-skills/spot-ai-mistakes.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.00145 | $0.01096 |
| Opus 5.5 | $0.00058 | $0.00438 |
| Sonnet 5.5 | $0.00029 | $0.00219 |
| Haiku 4.5 | $0.00015 | $0.00110 |
Grade A, and why
spot-ai-mistakes 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 2d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spot AI Mistakes
AI fails in patterned, learnable ways — it invents citations, states outdated facts with total confidence, agrees with whatever you imply, and fumbles arithmetic while sounding certain. Once you know the patterns and their tells, you catch most errors on sight. This maps the failure modes most relevant to how you use AI, the signs that give each away, and a fast check for the ones that would actually hurt — building the instinct so confident-wrong stops catching you off guard.
What This Skill Produces
- The failure patterns that matter for you — the specific ways AI goes wrong in your use (hallucinated facts, fabricated citations/quotes, outdated info, sycophancy, arithmetic slips, false precision, missed nuance, confident guessing)
- The tells for each — the signals that give a mistake away (suspiciously specific sources, confidence on recent/niche topics, agreeing too readily, round-number math)
- A fast check for the dangerous ones — a quick way to catch the errors that would actually cost you, without over-checking everything
- A calibrated trust level — where AI is reliable for your uses and where it isn't, so trust is earned per-domain not blanket
- The instinct, built — the habit of pattern-matching for these tells as you read AI output
Required Inputs
Ask for these if not provided:
- How you use AI — the domains and tasks (points at which failure modes matter most)
- A past miss — a time AI got something wrong on you, if you have one (great teacher)
- The stakes — what a missed error would cost in your use
- Your trust level now — where you're too trusting or too skeptical
Framework: Know The Patterns, Read The Tells
- Map failures to your use. The failure modes that matter depend on how you use AI — a coder cares about wrong APIs, a researcher about fake citations, a student about outdated facts. Focus on yours.
- Learn the tells. Each failure has signals: fabricated citations look oddly specific and un-Google-able; hallucinations spike on recent/niche topics; sycophancy shows as agreeing right after you hint at a preference; math errors hide in confident round numbers.
- Watch the confidence trap. AI's tone is uniform whether it's right or inventing — so confidence is not a signal of correctness. Judge by pattern and verification, never by how sure it sounds.
- Check the dangerous ones fast. For the errors that would actually hurt, a quick independent check (a source, a second tool, testing it) — don't over-verify the low-stakes stuff.
- Calibrate trust per domain. Trust AI more where it's reliable for you and less where it isn't — calibrated, not blanket trust or blanket suspicion.
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.
- 2d ago First seen · 64 lines · 145 tokens per session scan A 9cb774b358dd
spot-ai-mistakes is a skill published in the GitHub repository mohitagw15856/pm-claude-skills (1,449 stars, last pushed today), licensed MIT. It adds 145 tokens to every session and 1,096 once invoked, about $0.0006 per session on Opus 5.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-10-12.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…