general-rules

A small set of general coding-work rules for handling unclear instructions and checking documentation with current dates.

In plain words
What is it for?
It guides clarification of ambiguous rules and documentation checks for the tools and libraries used in a project.
Why use it?
It helps avoid silently choosing between conflicting requirements or relying on outdated technical information.

Cursor rule

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/dobryakov/cursor-rules/general-rules
Clone the repo
git clone --depth 1 https://github.com/dobryakov/cursor-rules
Per session 64 This file is loaded in full into every session.
When invoked 64 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.00064 $0.00064
Opus 5 $0.00032 $0.00032
Sonnet 5 $0.00013 $0.00013
Haiku 4.5 $0.00006 $0.00006

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

Security

Grade A, and why

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

en/rules/general-rules.mdc · 9 lines

What it actually says

General Rules

  • Always explicitly ask and clarify if any rules seem ambiguous or contradictory.
  • Use mcp context7 to check the documentation. Use the date +%Y-%m-%d command (if possible) to get the docs according the actual date.
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 · 9 lines · 64 tokens per session scan A 77ec5d00f771

Subscribe to this mod's changes

general-rules is a cursor rule published in the GitHub repository dobryakov/cursor-rules (2 stars, last pushed 2mo ago), licensed MIT. It adds 64 tokens to every session, about $0.0003 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.