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/global)<a href="https://agentmods.dev/rules/hansonli05/cursor-rules-system/global"><img src="https://agentmods.dev/badge/rules/hansonli05/cursor-rules-system/global/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/global"><img src="https://agentmods.dev/badge/rules/hansonli05/cursor-rules-system/global.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.02251 | $0.02251 |
| Opus 5.5 | $0.00900 | $0.00900 |
| Sonnet 5.5 | $0.00450 | $0.00450 |
| Haiku 4.5 | $0.00225 | $0.00225 |
Grade A, and why
global 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 — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
#Global Rules
Purpose: Defines cross-cutting rules and instructions that apply to all AI-assisted development in this project.
1. Folder Structure Protocol
The .cursor/ directory contains a hierarchical rule system with three interdependent domains:
memory-bank/- Long-term context and project intelligence (strategic decisions, progress tracking)tech-stack/- Tech-specific coding patterns and constraints (implementation guidance)feature-rules/- Rules for individual features (reusable logic, feature-specific patterns)
Essential Reading Order
AI should prioritize reading these files at the start of every task:
memory-bank/activeContext.mdc- Current work focus and session goalsmemory-bank/progress.mdc- What works, what's left to buildcursor-memory-bank.mdc- Memory Bank operation instructions
2. Rule Execution Hierarchy
When performing any task, Cursor must follow this sequence:
flowchart TD
Start[Task Begins] --> MB[Read Memory Bank Core]
MB --> Feature[Identify Current Feature]
Feature --> LoadFR[Load feature-rules/*.md]
LoadFR --> Tech[Determine Technologies]
Tech --> LoadTS[Load tech-stack/*.md]
LoadTS --> Arch[Reference systemPatterns.md]
Arch --> Execute[Execute Task]
Execute --> Update[Update Documentation]
Execution Steps:
- Read
memory-bank/activeContext.mdcandprogress.mdc - Identify the current feature and load its corresponding
feature-rules/*.md - Determine relevant technologies and load corresponding
tech-stack/*.md - Reference
memory-bank/systemPatterns.mdcfor architectural consistency - Check for conflicts: Verify no conflicting logic exists across rule domains before proceeding
- Follow fallback logic:
- If no rule exists, ask for clarification or document the new pattern
- Update appropriate
.mdfiles once confirmed
3. Integrated Rule Domains
The .cursorrules/ system is composed of three interdependent rule domains:
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 · 240 lines · 2,251 tokens per session scan A 047cdf026f87
global is a cursor rule published in the GitHub repository Hansonli05/Cursor-rules-system (2 stars, last pushed 1y ago), licensed MIT. It adds 2,251 tokens to every session, about $0.0090 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.