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/hansonli05/cursor-rules-system/productcontextgit clone --depth 1 https://github.com/Hansonli05/Cursor-rules-systemWhat 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.00416 | $0.00416 |
| Opus 5 | $0.00208 | $0.00208 |
| Sonnet 5 | $0.00083 | $0.00083 |
| Haiku 4.5 | $0.00042 | $0.00042 |
Grade A, and why
productContext 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.
What it actually says
Product Context
Problem Statement
[Detailed description of the problem you're solving]
- [Specific pain point 1]
- [Specific pain point 2]
- [Market gap or opportunity]
Target Users
Primary Users
- [User Type 1]: [Description, needs, behaviors]
- [User Type 2]: [Description, needs, behaviors]
Secondary Users
- [User Type 3]: [Description, needs, behaviors]
User Stories/Use Cases
Core User Flows
-
[Primary Flow Name]
- User wants to [goal]
- Steps: [brief flow description]
- Success: [end state]
-
[Secondary Flow Name]
- User wants to [goal]
- Steps: [brief flow description]
- Success: [end state]
Product Goals
Business Goals
- [Business objective 1]
- [Business objective 2]
- [Success metrics]
User Experience Goals
- [Key experience principles]
Competitive Landscape
- [Competitor 1]: [What they do well, gaps]
- [Competitor 2]: [What they do well, gaps]
- Our Differentiator: [What makes this product unique]
Success Metrics
Product Principles
Note: This context drives feature prioritization and user experience decisions. Update when user research reveals new insights or market conditions change.
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 · 63 lines · 416 tokens per session scan A 0f47a07190f6
productContext is a cursor rule published in the GitHub repository Hansonli05/Cursor-rules-system (2 stars, last pushed 1y ago), licensed MIT. It adds 416 tokens to every session, about $0.0021 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.
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.
family-instance-domain-actions
Family instance domain action implementation patterns.