systemPatterns

A project architecture and design-pattern template describing system parts, boundaries, connections, data flows, and reusable coding approaches. Most of the supplied content is still placeholder text.

In plain words
What is it for?
Use it to document components, internal and external systems, integrations, design decisions, and expected data flows.
Why use it?
It can give an agent a shared map of how a system is meant to be organized, but this file currently provides little project-specific guidance until it is completed.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/hansonli05/cursor-rules-system/systempatterns
Clone the repo
git clone --depth 1 https://github.com/Hansonli05/Cursor-rules-system

Made for: Cursor.

Per session 902 This file is loaded in full into every session.
When invoked 902 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00902 $0.00902
Opus 5 $0.00451 $0.00451
Sonnet 5 $0.00180 $0.00180
Haiku 4.5 $0.00090 $0.00090

Measured yesterday against content hash 6faaa039f55b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

.cursor/rules/memory-bank/systemPatterns.mdc · 103 lines

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

  1. [Flow Name 1]: [Source] → [Processing] → [Destination]
  2. [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]

Read the full file on GitHub · 103 lines

Changes

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.

  1. yesterday First seen · 103 lines · 902 tokens per session scan A 6faaa039f55b

Subscribe to this mod's changes

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.0045 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.