cursorrules

A rule that requires generated code to pass through a review service before it is shown to the user.

In plain words
What is it for?
Use it for coding requests where every draft must be submitted for review and revised or released according to the service's response.
Why use it?
It adds a required draft, audit, and repair cycle to code generation. The input does not describe the review service's exact checks.

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/sim-xia/blind-auditor/cursorrules
Clone the repo
git clone --depth 1 https://github.com/Sim-xia/Blind-Auditor

Made for: Cursor.

Per session 144 This file is loaded in full into every session.
When invoked 144 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.00144 $0.00144
Opus 5 $0.00072 $0.00072
Sonnet 5 $0.00029 $0.00029
Haiku 4.5 $0.00014 $0.00014

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

Security

Grade A, and why

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

.cursorrules · 16 lines

What it actually says

代码生成规则

CRITICAL INSTRUCTION: 每当你为用户生成代码时,你必须遵循以下流程:

  1. 内部生成代码(不要直接输出)
  2. 调用 MCP 工具 submit_draft,传入代码和语言参数
  3. 严格遵守工具返回的指令

示例流程:

  • 如果返回审计指令,立即切换为审计员角色进行代码审查
  • 如果返回修复指令,按要求修正代码并重新提交
  • 如果返回放行指令,将最终代码展示给用户

重要: 此规则适用于所有代码生成请求,无例外。

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 · 16 lines · 144 tokens per session scan A fddcfaf1d4a5

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository Sim-xia/Blind-Auditor (11 stars, last pushed 8mo ago), licensed MIT. It adds 144 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-30.