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/ai-feature-prd)<a href="https://agentmods.dev/rules/mohitagw15856/pm-claude-skills/ai-feature-prd"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/ai-feature-prd/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/ai-feature-prd"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/ai-feature-prd.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.01032 |
| Opus 5 | $0.00048 | $0.00516 |
| Sonnet 5 | $0.00019 | $0.00206 |
| Haiku 4.5 | $0.00010 | $0.00103 |
Grade A, and why
ai-feature-prd 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Feature PRD Skill
AI features break the normal PRD because the system is probabilistic: it will be wrong sometimes, and the product must be designed around that, not in denial of it. This skill extends a standard PRD with the AI-specific sections that decide whether the feature is trustworthy — the UX of uncertainty, the eval bar, guardrails, and what happens when the model is wrong.
Required Inputs
Ask for these only if they aren't already provided:
- The user problem and why an AI/probabilistic approach fits it (vs. deterministic rules).
- What "good" looks like to the user, and the cost of a wrong answer (low-stakes vs. high-stakes).
- Inputs available — context/data the model can use; privacy constraints.
- Trust level needed — can the user verify the output, or must it be near-perfect?
Reads from / Writes to the Brain
If a professional-brain exists, read context.md (product, users, voice)
and knowledge/strategy.md first; write the feature to entities/ and any scoping decision to decisions/,
each provenance-tagged.
Output Format
AI Feature PRD: [feature]
1. Problem & why AI — the user problem, and why a model (not rules) is the right tool. If rules would do, say so.
2. Experience — the core flow, and crucially the UX of uncertainty: how confidence is shown, how the user verifies/edits, and how errors are made cheap to recover from. AI features live or die here.
3. Model approach — prompt / fine-tune / RAG / agent (link rag-design-doc or agent-spec), the model tier, and why.
4. Quality bar & evaluation — the metrics and the explicit ship threshold; reference an ai-eval-plan. State the acceptable error rate given the stakes.
5. Guardrails & safety — what the feature must never do, input/output filtering, and handling of harmful/PII/out-of-scope inputs.
6. Fallback behaviour — what happens when the model is unsure, wrong, slow, or down: graceful degradation, "I'm not sure" states, human handoff. No silent confident errors.
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 · 71 lines · 95 tokens per session scan A bc2d313d5ea0
ai-feature-prd 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,032 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
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.