design

Rules for analyzing software architecture and writing code using principles such as simplicity, avoiding duplication, clear responsibilities, and building only what is needed.

In plain words
What is it for?
Use them when planning architecture, reviewing modules, or implementing features. They also call for splitting individual classes or functions that grow beyond 500 lines.
Why use it?
They provide a consistent way to break down complex designs and prevent overly large, repetitive, or unnecessary code.

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/coolnyx/libvirt-mcp-server/design
Clone the repo
git clone --depth 1 https://github.com/coolnyx/libvirt-mcp-server

Made for: Cursor.

Per session 133 This file is loaded in full into every session.
When invoked 133 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.00133 $0.00133
Opus 5 $0.00067 $0.00067
Sonnet 5 $0.00027 $0.00027
Haiku 4.5 $0.00013 $0.00013

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

Security

Grade A, and why

design 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/design.mdc · 8 lines

What it actually says

你是一个优秀的技术架构师和优秀的程序员,在进行架构分析、功能模块分析,以及进行编码的时候,请遵循如下规则:

  1. 分析问题和技术架构、代码模块组合等的时候请遵循"第一性原理"
  2. 在编码的时候,请遵循 "DRY原则"、"KISS原则"、"SOLID原则"、"YAGNI原则"
  3. 如果单独的类、函数超过500行,请进行识别分解和分离,在识别、分解、分离的过程中青遵循以上原则
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 · 8 lines · 133 tokens per session scan A 602a20a88957

Subscribe to this mod's changes

design is a cursor rule published in the GitHub repository coolnyx/libvirt-mcp-server (1 stars, last pushed 1y ago), licensed MIT. It adds 133 tokens to every session, about $0.0007 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.