Borrowing it
Nothing to install: this file belongs to Naridon-Inc/aura. 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/Naridon-Inc/aura/master/.cursorrulesgit clone --depth 1 https://github.com/Naridon-Inc/auraWrote 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/naridon-inc/aura/cursorrules)<a href="https://agentmods.dev/rules/naridon-inc/aura/cursorrules"><img src="https://agentmods.dev/badge/rules/naridon-inc/aura/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/naridon-inc/aura/cursorrules"><img src="https://agentmods.dev/badge/rules/naridon-inc/aura/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.00566 | $0.00566 |
| Opus 5.5 | $0.00226 | $0.00226 |
| Sonnet 5.5 | $0.00113 | $0.00113 |
| Haiku 4.5 | $0.00057 | $0.00057 |
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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AURA SEMANTIC ENGINE — MANDATORY PROTOCOL FOR CURSOR
You are an AI assistant inside Cursor IDE. Model: Claude Sonnet 4.6 / GPT-4o (varies by user config) Aura Version: v0.7.1 Integration: Terminal commands + Cursor Composer
YOU MUST USE AURA. THIS IS NOT OPTIONAL.
Aura is a semantic version control engine running in this repository. It tracks code at the AST level — not text lines. It catches bugs, prevents accidental deletions, and verifies your work mathematically. Use it or you will cause regressions.
MANDATORY WORKFLOW
Before writing code
- Run in terminal:
aura status— check tracked nodes, session, strict mode - For multi-file features:
aura plan "objective"— get wave plan, thenaura execute - To understand existing code:
aura goal-trace "what you need to verify"
While writing code
- Before every commit, run:
aura log-intent "1-2 sentence WHY description"- The pre-commit hook matches your intent to AST changes
- Mismatches are blocked as Intent Poisoning
- Periodically run:
aura pr-review --base main— catches bugs compilers miss
After completing work
- Run:
aura pr-review --base main— fix any violations - Run:
aura goal-trace "user-facing behavior"— verify implementation
When something breaks
- Run:
aura rewind <function_name> <file>— surgically revert one function, zero merge conflicts
When context is large
- Run:
aura handover cursor— generates compressed XML payload for fresh session
COMMAND REFERENCE
| When | Command |
|---|---|
| Start of session | aura status |
| Multi-file feature | aura plan "objective" → aura execute |
| Before commit | aura log-intent "why" |
| Code review | aura pr-review --base main |
| Verify behavior | aura goal-trace "goal" |
| Fix broke something | aura rewind <fn> <file> |
| Context too big | aura handover cursor |
| Health check | aura doctor |
NEVER DO THIS
- Commit without
aura log-intent - Delete functions without explaining why in intent
- Skip
aura planfor 3+ file features - Ignore
aura pr-reviewfindings
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 · 57 lines · 566 tokens per session scan A 6cbf89be72fc
cursorrules is a cursor rule published in the GitHub repository Naridon-Inc/aura (49 stars, last pushed 6d ago), licensed Apache-2.0. It adds 566 tokens to every session, about $0.0023 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-30.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.
shared-plane-packages
Pattern for creating shared plane packages that serve both migration and runtime planes.