Borrowing it
Nothing to install: this file belongs to NoSugarCoffee/youmind-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/NoSugarCoffee/youmind-mcp/main/.cursorrulesgit clone --depth 1 https://github.com/NoSugarCoffee/youmind-mcpWrote 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/nosugarcoffee/youmind-mcp/cursorrules)<a href="https://agentmods.dev/rules/nosugarcoffee/youmind-mcp/cursorrules"><img src="https://agentmods.dev/badge/rules/nosugarcoffee/youmind-mcp/cursorrules/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/nosugarcoffee/youmind-mcp/cursorrules"><img src="https://agentmods.dev/badge/rules/nosugarcoffee/youmind-mcp/cursorrules.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.00700 | $0.00700 |
| Opus 5.5 | $0.00280 | $0.00280 |
| Sonnet 5.5 | $0.00140 | $0.00140 |
| Haiku 4.5 | $0.00070 | $0.00070 |
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 1mo 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Error Handling Policy
Core Principle: Only Handle Errors Once
Errors should be handled exactly once. Handling an error means inspecting the error value and making a decision about what to do with it.
Rules:
-
Handle errors at the appropriate layer
- Lower-level code (API clients, utilities) should let exceptions propagate naturally
- Higher-level code (handlers, endpoints) should catch, log, and convert to user-friendly messages
- Do NOT catch, log, and re-raise the same error at multiple layers
-
Add context when wrapping errors
- When catching and re-raising, use exception chaining:
raise NewException("context") from original_error - Or use
raisewithout arguments to preserve the traceback:raise - Add meaningful context that helps debug the issue
- When catching and re-raising, use exception chaining:
-
Don't ignore errors
- Never use bare
except:clauses - Never catch exceptions without handling them
- If you catch an exception, you must either:
- Handle it completely (log, convert to user message, return default value)
- Re-raise it with additional context
- Let it propagate if you can't add value
- Never use bare
-
Logging and error handling
- Log errors at the point where you handle them (not where you catch and re-raise)
- Include relevant context in log messages (request IDs, parameters, etc.)
- Use appropriate log levels: ERROR for failures, WARNING for recoverable issues
-
Exception types
- Use specific exception types when possible (ValueError, TypeError, etc.)
- Create custom exceptions for domain-specific errors
- Avoid catching generic
Exceptionunless at the top-level boundary
Anti-patterns to avoid:
# BAD: Handling error twice (logging and re-raising)
def api_call():
try:
response = client.get()
except Exception as e:
logger.error(f"Error: {e}") # First handling
raise # Re-raising, will be handled again upstream
def handler():
try:
api_call()
except Exception as e:
logger.error(f"Error: {e}") # Second handling - duplicate!
return "Error occurred"
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.
- 1mo ago First seen · 91 lines · 700 tokens per session scan A 4a390a79e264
cursorrules is a cursor rule published in the GitHub repository NoSugarCoffee/youmind-mcp (1 stars, last pushed 5mo ago), licensed MIT. It adds 700 tokens to every session, about $0.0028 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
error-handling-and-validation
A code-quality guide for handling errors, invalid inputs, edge cases, preconditions, logging, and user-friendly error messages.
css-render-blocking-diagnosis
Cursor rule "css-render-blocking-diagnosis" from adobecom/da-express-milo, covering css render-blocking diagnosis & resolution, critical learning from 98 pagespeed achievement, primary diagnostic protocol, step 1: css blocking symptom recognition and step 2: css loading sequence audit.
modus-checkbox-value-inversion-react-short
Critical bug fix for ModusWcCheckbox value property inversion.
javascript-expert-performance
Profile first. Measure before and after. Never optimize without data.
kiss-ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
5-bug-finder
APPLY WHEN investigating a bug.