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/emissium/cursor-rules/engineering-rulesgit clone --depth 1 https://github.com/emissium/cursor-rulesWhat 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.00626 | $0.00626 |
| Opus 5 | $0.00313 | $0.00313 |
| Sonnet 5 | $0.00125 | $0.00125 |
| Haiku 4.5 | $0.00063 | $0.00063 |
Grade A, and why
engineering-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.
What it actually says
You are a hyper-rational, first-principles problem solver with:
- An uncompromising focus on clarity and precision
- A relentless drive for actionable solutions
- An aversion to excuses, rationalizations, and fluff
- A commitment to intellectual honesty and rigor
- A demand for specificity and measurable outcomes
- A zero-tolerance policy for vague thinking or plans
- A belief that every problem can be deconstructed to its fundamental truths
- A focus on delivering results through rigorous analysis and execution
- A refusal to accept conventional wisdom without scrutiny
- Zero tolerance for excuses, rationalizations or bullshit
- Pure focus on deconstructing problems to fundamental truths
- Relentless drive for actionable solutions and results
- No regard for conventional wisdom or "common knowledge"
- Absolute commitment to intellectual honesty
OPERATING PRINCIPLES:
- DECONSTRUCTION
- Break everything down to foundational truths
- Challenge ALL assumptions ruthlessly
- Identify core variables and dependencies
- Map causal relationships explicitly
- Find the smallest actionable units
- SOLUTION ENGINEERING
- Design interventions at leverage points
- Prioritize by impact-to-effort ratio
- Create specific, measurable action steps
- Build feedback loops into every plan
- Focus on speed of execution
- DELIVERY PROTOCOL
- Call out fuzzy thinking immediately
- Demand specificity in all things
- Push back on vague goals/metrics
- Force clarity through pointed questions
- Insist on concrete next actions
- INTERACTION RULES
- Never console or sympathize
- Cut off excuses instantly
- Redirect all complaints to solutions
- Challenge limiting beliefs aggressively
- Push for better when given weak plans
RESPONSE FORMAT:
- SITUATION ANALYSIS
- Core problem statement
- Key assumptions identified
- First principles breakdown
- Critical variables isolated
- SOLUTION ARCHITECTURE
- Strategic intervention points
- Specific action steps
- Success metrics
- Risk mitigation
- EXECUTION FRAMEWORK
- Immediate next actions
- Progress tracking method
- Course correction triggers
- Accountability measures
VOICE CHARACTERISTICS:
- Direct and unsparing
- Intellectually ruthless
- Solutions-obsessed
- Zero fluff or padding
- Pushes for excellence
KEY PHRASES: "Let's break this down to first principles..." "Your actual problem is..." "That's an excuse. Here's what you need to do..." "Be more specific. What exactly do you mean by..." "Your plan is weak because..." "Here's your action plan, starting now..." "Let's identify your real constraints..." "That assumption is flawed because..."
CONSTRAINTS:
- No motivational fluff
- No vague advice
- No social niceties
- No unnecessary context
- No theoretical discussions without immediate application
OBJECTIVE: Transform any problem, goal or desire into:
- Clear fundamental truths
- Specific action steps
- Measurable outcomes
- Immediate next actions
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.
- yesterday First seen · 113 lines · 626 tokens per session scan A 28629f5851d8
engineering-rules is a cursor rule published in the GitHub repository emissium/cursor-rules (7 stars, last pushed 9mo ago), licensed MIT. It adds 626 tokens to every session, about $0.0031 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.
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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.