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.
git 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/gsd)<a href="https://agentmods.dev/rules/naridon-inc/aura/gsd"><img src="https://agentmods.dev/badge/rules/naridon-inc/aura/gsd/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/gsd"><img src="https://agentmods.dev/badge/rules/naridon-inc/aura/gsd.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.00619 | $0.00619 |
| Opus 5.5 | $0.00248 | $0.00248 |
| Sonnet 5.5 | $0.00124 | $0.00124 |
| Haiku 4.5 | $0.00062 | $0.00062 |
Grade A, and why
gsd 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Aura — Mandatory Agent Workflow
You have access to the aura CLI. These commands are NOT optional. Use them as described below.
HARD RULES — Follow These, No Exceptions
Before you write ANY code
- Run
aura statusto see what's tracked (logic nodes, checkpoints). - If the task involves 3+ files or a new feature, run
aura plan "objective". Review the gray areas, lock decisions, then follow the wave plan. Do NOT skip this — it prevents you from building on wrong assumptions.
While writing code
- Before editing a file, think about which specific functions need to change. Run
aura prove --goal "what you're trying to achieve"to understand the existing logic paths. - Run
aura pr-review --base mainperiodically to catch layer violations and bugs as you go. - Before every commit, run
aura log-intent "1-2 sentence description of WHY". The gatekeeper matches your words to AST changes.
After completing work
- Run
aura pr-review --base main. Fix any invariant violations or security issues it finds. - Run
aura prove --goal "user-facing behavior". If it returns warnings, investigate. - If the review found violations, run
aura fixto auto-resolve them.
When context is getting large
- Run
aura handover cursor. It generates a compressed XML payload. Ask the user to start fresh with this payload — saves ~90% of tokens.
Command Quick Reference
| Trigger | Command | What it does |
|---|---|---|
| Planning a feature | aura plan "objective" |
Gray areas + locked wave plan |
| Executing a plan | aura execute or aura execute --auto |
Run waves (--auto skips confirmations) |
| Something broke | aura rewind <function> <file> |
Revert one function to last safe state |
| Verify a feature | aura prove --goal "..." |
Mathematical proof via AST tracing |
| Before a commit | aura log-intent "why" |
Bind reasoning to AST changes |
| Before a merge | aura pr-review --base main |
Semantic diff + bug/security scan |
| Auto-fix violations | aura fix |
Shadow branch auto-correction |
| Screenshot to code | aura design-copy img.png |
Gemini vision generates React/HTML/Vue |
| Context too big | aura handover <agent> |
Compress to XML handover payload |
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 · 42 lines · 619 tokens per session scan A 15791aef8385
gsd is a cursor rule published in the GitHub repository Naridon-Inc/aura (49 stars, last pushed 5d ago), licensed Apache-2.0. It adds 619 tokens to every session, about $0.0025 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-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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.