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/ertra/pm-brain-for-cursor/product-sensegit clone --depth 1 https://github.com/ertra/pm-brain-for-cursorWrote 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/ertra/pm-brain-for-cursor/product-sense)<a href="https://agentmods.dev/rules/ertra/pm-brain-for-cursor/product-sense"><img src="https://agentmods.dev/badge/rules/ertra/pm-brain-for-cursor/product-sense.svg" alt="Measured on agentmods" 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.00386 | $0.00386 |
| Opus 5 | $0.00193 | $0.00193 |
| Sonnet 5 | $0.00077 | $0.00077 |
| Haiku 4.5 | $0.00039 | $0.00039 |
Grade A, and why
product-sense 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 6d 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.
What it actually says
Product sense (coaching layer)
Before generating a product brief or PRD in this repo, follow PRODUCT-RULES.md.
- Read
PRODUCT-RULES.mdwhen the user asks for a brief, PRD, one-pager, feature pitch, or similar — including ad-hoc prompts (not only slash commands). - Apply the "When the gate applies" table in that file:
- Product brief → run the braindump gate (3–5 product-sense questions + sufficiency checklist) before opening templates or the
create-product-briefskill's research step. - PRD → run the gate only if no brief exists (
01-product-brief.mdin the feature hub or an explicit brief path from the user). Otherwise proceed with the doc skill. - IFA, support article, competitive landscape, interview-frameworks → no braindump gate.
- Product brief → run the braindump gate (3–5 product-sense questions + sufficiency checklist) before opening templates or the
- Do not open
02-templates/or write structured outlines until the sufficiency checklist passes or the user says "skip braindump" (log the override perPRODUCT-RULES.md). - When a doc skill is invoked (
create-product-brief,create-prd), follow that skill's Step 0.5 if present — it implements this gate in detail.
Doc pack workflow (order, feature hubs) remains in AGENTS.md and pm-brain-doc-workflow.mdc.
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.
- 6d ago First seen · 21 lines · 386 tokens per session scan A 2c9aa628c567
product-sense is a cursor rule published in the GitHub repository ertra/pm-brain-for-cursor (22 stars, last pushed 3mo ago), licensed MIT. It adds 386 tokens to every session, about $0.0019 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
slice-tasks
PLANNING SPINE STEP 2 of 3 — Slice the work: break a scoped PRD into vertical-slice stories in specs/epics/. Use after scope-work (step 1), before plan-work (step 3). Not a substitute for scope-work or plan-work.
elite-orchestrator
Elite orchestrator for mission-critical, enterprise-scale tasks requiring strategic coordination of 7+ agents across all domains. Makes architectural decisions, manages risk, ensures business continuity, and delivers enterprise-grade outcomes. Use for platform migrations, security incidents, multi-system integrations…
project-onboarding-rule
Automatically onboards existing projects into the AI-driven development workflow.
linear-in-review
After finishing a Linear issue, set its status to In Review (never Done).
sprint-planning
BMAD BMM Agent: sprint-planning.
workflow-examples
CRITICAL: Contains mandatory examples for correct workflow implementation. DO NOT assume workflow patterns without consulting this documentation first.