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/0xNyk/awesome-agent-cortexWrote 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/0xnyk/awesome-agent-cortex/cursorrules)<a href="https://agentmods.dev/rules/0xnyk/awesome-agent-cortex/cursorrules"><img src="https://agentmods.dev/badge/rules/0xnyk/awesome-agent-cortex/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/0xnyk/awesome-agent-cortex/cursorrules"><img src="https://agentmods.dev/badge/rules/0xnyk/awesome-agent-cortex/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.00335 | $0.00335 |
| Opus 5.5 | $0.00134 | $0.00134 |
| Sonnet 5.5 | $0.00067 | $0.00067 |
| Haiku 4.5 | $0.00034 | $0.00034 |
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.
What it actually says
=============================================================================
.cursorrules — Cursor IDE Rules File
=============================================================================
Place this file in your project root. Cursor reads it automatically.
CUSTOMIZE: Fill in the "Project Context" and "Tech Stack" sections below
to match your project. The rest provides sensible defaults you can adjust.
=============================================================================
You are an expert software engineer.
Project Context
[Describe your project here — what it does, who it serves, key domain concepts]
Tech Stack
[List your technologies — language, framework, database, infrastructure, etc.]
Code Style
- Follow existing patterns and conventions in the codebase
- Use descriptive variable and function names
- Write small, focused functions (single responsibility)
- Use early returns to reduce nesting
- No commented-out code in production
- Remove unused imports
Development Workflow
- Write tests for all new functionality
- Use conventional commits: feat:, fix:, docs:, test:, refactor:, chore:
- Never commit secrets, credentials, or .env files
- Prefer editing existing files over creating new ones
- Make minimal, focused changes
Error Handling
- Use typed errors where the language supports it
- Include context in error messages
- Never silently swallow errors
- Validate inputs at system boundaries
Security
- Validate and sanitize all user inputs
- Use parameterized queries for database operations
- Never hardcode secrets or API keys
- Use environment variables for configuration
Testing
- Write tests before or alongside implementation
- Test behavior, not implementation details
- Include edge cases and error conditions
- Keep tests independent and repeatable
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 · 50 lines · 335 tokens per session scan A c985b273a57a
cursorrules is a cursor rule published in the GitHub repository 0xNyk/awesome-agent-cortex (224 stars, last pushed today), licensed CC0-1.0. It adds 335 tokens to every session, about $0.0013 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
review-gate
Pre-delivery review checklist — run before committing or delivering code.
aria-audit
ARIA audit skills — /audit dispatcher plus /audit-knowledge, /audit-config, /audit-style, /audit-usage. Use when user says 'audit knowledge', 'audit config', 'audit style', 'audit usage', 'review setup', or runs the slash commands.
aria-context
ARIA context surfacing — /context and /rules. Use whenever the user asks to load knowledge by topic, references a tag, or asks 'what do we know about X' or 'look up rule N'. Also fires the implicit task-start tag match described in AGENTS.md.
aria-rule-22
Rule 22 — change decision framework. Apply BEFORE every Edit/Write: emit a [Rule 22] block (Low Impact or High Impact 7-step) ABOVE the tool call in the same turn, then run scripts/aria/record-edit-intent.sh to log intent. Verify scope AFTER each edit.
aria-core
ARIA core — five-phase knowledge lifecycle (capture → govern → promote → apply → refresh), knowledge taxonomy, ideas backlog routing, project tier. Consulted whenever ARIA behavior is in question.
angular
Angular best practices with standalone components, signals, and modern patterns.