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 agentmods add rules/chatprd/cursor-plugin/product-aware-developmentgit clone --depth 1 https://github.com/ChatPRD/cursor-pluginWhat 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 | $0.00200 | $0.00200 |
| Opus 5 | $0.00100 | $0.00100 |
| Sonnet 5 | $0.00040 | $0.00040 |
| Haiku 4.5 | $0.00020 | $0.00020 |
Grade A, and why
product-aware-development 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 yesterday.
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.
What it actually says
Product-aware development
- When implementing a feature with a corresponding PRD, reference specific requirements rather than making assumptions about intended behavior.
- Handle edge cases and error states that product specs call out — empty states, loading states, error recovery, and boundary conditions.
- If an implementation decision deviates from the spec, note it in a code comment or commit message so it can be tracked back to the PRD.
- Acceptance criteria from PRDs map to test cases. When writing tests, cover the scenarios the spec defines.
- Keep user-facing copy, labels, and flows consistent with what the PRD specifies.
- Check the local
prd/directory for relevant specs before starting work on a feature. - When a PRD states user or business goals, look for opportunities to improve the UX or implementation beyond the literal spec to better achieve those goals.
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.
- yesterday First seen · 15 lines · 200 tokens per session scan A c3dfb98093dc
product-aware-development is a cursor rule published in the GitHub repository ChatPRD/cursor-plugin (5 stars, last pushed 6mo ago), licensed MIT. It adds 200 tokens to every session, about $0.0010 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-31.
Other cursor rules, from other repositories
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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.