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/naridon-inc/aura/cursorrulesgit clone --depth 1 https://github.com/Naridon-Inc/auraWhat 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.00566 | $0.00566 |
| Opus 5 | $0.00283 | $0.00283 |
| Sonnet 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 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.
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.
- 2d 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 (45 stars, last pushed 12d ago), licensed Apache-2.0. It adds 566 tokens to every session, about $0.0028 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-30.
Other cursor rules, from other repositories
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.
java-springboot-jpa-cursorrules-prompt-file
description: "Cursor rules for Java development with Springboot and JPA integration." globs: / alwaysApply: false.
ehs-ims-conventions
EHS IMS app — RBAC, data layer, tRPC, migrations, AI boundaries.
002-verify-before-act
Requires Claude to read before writing, verify before installing, and confirm before destructive operations.
swift-development
Swift development: SwiftUI, Combine, async/await, iOS patterns, and Apple platform conventions.
readme-best-practices
README Best Practices - enforces high-quality README patterns when creating or editing README files.