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/Hansonli05/Cursor-rules-systemWrote 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/hansonli05/cursor-rules-system/systempatterns)<a href="https://agentmods.dev/rules/hansonli05/cursor-rules-system/systempatterns"><img src="https://agentmods.dev/badge/rules/hansonli05/cursor-rules-system/systempatterns/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/hansonli05/cursor-rules-system/systempatterns"><img src="https://agentmods.dev/badge/rules/hansonli05/cursor-rules-system/systempatterns.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.00902 | $0.00902 |
| Opus 5.5 | $0.00361 | $0.00361 |
| Sonnet 5.5 | $0.00180 | $0.00180 |
| Haiku 4.5 | $0.00090 | $0.00090 |
Grade A, and why
systemPatterns 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 2mo 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
System Patterns
Architecture Overview
High-Level Architecture
[Describe your system's overall architecture - e.g., client-server, microservices, monolith, etc.]
Core Components
- [Component 1]: [Purpose and responsibilities]
- [Component 2]: [Purpose and responsibilities]
- [Component 3]: [Purpose and responsibilities]
System Boundaries
- Internal Systems: [Components you control]
- External Systems: [Third-party services, APIs]
- Integration Points: [How components communicate]
Key Design Patterns
Architectural Patterns
-
[Pattern 1]: [When and how it's used]
- Context: [Why this pattern was chosen]
- Implementation: [How it's implemented in your system]
-
[Pattern 2]: [When and how it's used]
- Context: [Why this pattern was chosen]
- Implementation: [How it's implemented in your system]
Code Patterns
-
[Code Pattern 1]: [Description]
- Usage: [When to apply this pattern]
- Example: [Brief example or reference]
-
[Code Pattern 2]: [Description]
- Usage: [When to apply this pattern]
- Example: [Brief example or reference]
Data Flow
Primary Data Flows
- [Flow Name 1]: [Source] → [Processing] → [Destination]
- [Flow Name 2]: [Source] → [Processing] → [Destination]
State Management
- Global State: [How global state is managed]
- Local State: [Patterns for component state]
- Persistence: [How data is persisted]
Security Patterns
- Authentication: [How users are authenticated]
- Authorization: [How permissions are managed]
- Data Protection: [How sensitive data is protected]
- API Security: [How APIs are secured]
Performance Patterns
- Caching Strategy: [How caching is implemented]
- Loading Patterns: [How data loading is optimized]
- Optimization Strategies: [Key performance optimizations]
Error Handling
- Error Boundaries: [How errors are contained]
- Logging Strategy: [How errors are logged and monitored]
- User Error Experience: [How errors are presented to users]
- Recovery Patterns: [How the system recovers from 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.
- 2mo ago First seen · 103 lines · 902 tokens per session scan A 6faaa039f55b
systemPatterns is a cursor rule published in the GitHub repository Hansonli05/Cursor-rules-system (2 stars, last pushed 1y ago), licensed MIT. It adds 902 tokens to every session, about $0.0036 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-08-31.
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.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.