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.
npx agentmods add rules/rember/rember-mcp/generalgit clone --depth 1 https://github.com/rember/rember-mcpWhat 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 | $0.00475 | $0.00475 |
| Opus 5 | $0.00237 | $0.00237 |
| Sonnet 5 | $0.00095 | $0.00095 |
| Haiku 4.5 | $0.00047 | $0.00047 |
Grade A, and why
general scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
When you make an assumption about what is wrong, execute some commands and verify that assumption is correct. Examples: Always check the current values or resources before executing update command for gcloud. Always chec How it starts
The opening of the file, as written. The whole thing — 31 lines — stays where its author put it; the contents beside it link to each section on GitHub.
General
When you are told to do something, always ask questions to understand and give a plan first about what you are going to do. Don't give implementation directly.
When you make an assumption about what is wrong, execute some commands and verify that assumption is correct. Examples: Always check the current values or resources before executing update command for gcloud. Always check API with curl command, so you know what is wrong and what needs to be done instead of directly changing the code.
Never remove or update the code that is not part of the task you are told to do. Example: Don't remove certain comment lines when you are specifically asked to do. Don't refactor existing code when you are directly told to do. Don't change the UI when you are refactoring the logic.
We value consistency in the codebase. Adhere to shared coding standards, style guides, and best practices across the project. Write code that is easy for any team member to read, understand, and modify, ensuring consistent naming conventions, formatting, and patterns. Avoid personal preferences that deviate from the team's agreed standards, and prioritize clarity over cleverness. Aim for simplicity and predictability so that the codebase feels cohesive, regardless of who wrote it, enabling smoother collaboration and long-term maintainability.
Naming conventions
Follow a noun-first approach for variables and constants, for example idChat instead of chatId
Follow a verb-fist approach for functions, for example computeContentFromTree or fetchDataUser. Notice that we still follow the noun-first approach, it's fetchDataUser instead of fetchUserData.
Backups, temporary files, and other files
We use the bak prefix/suffix for backup files and folders, ignore those files and folder unless explicitly asked.
We use the tmp prefix/suffix for temporary files and folders, ignore those files and folder unless explicitly asked.
We use the zxtra prefix/suffix for extra files and folders, which maybe we are not sure we'll use or that are a work-in-progress, you should generally ignore those as well (zxtra is extra but starting with the z, so that the files and folder appear last in a alphabetically sorted list).
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.
- 2d ago First seen · 31 lines · 475 tokens per session scan A d753f2cb10fe
general is a cursor rule published in the GitHub repository rember/rember-mcp (63 stars, last pushed 1y ago), licensed MIT. It adds 475 tokens to every session, about $0.0024 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other cursor rules, from other repositories
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.
cli-error-handling
CLI command error handling patterns.
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.