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/flores-ac/cursor-cortex/cortexgit clone --depth 1 https://github.com/flores-ac/cursor-cortexWhat 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.00000 | $0.00229 |
| Opus 5 | $0.00000 | $0.00114 |
| Sonnet 5 | $0.00000 | $0.00046 |
| Haiku 4.5 | $0.00000 | $0.00023 |
Grade A, and why
cortex 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 today.
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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- today First seen · 30 lines · 0 tokens per session scan A 5b891a90f29f
cortex is a cursor rule published in the GitHub repository flores-ac/cursor-cortex (4 stars, last pushed 17d ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 229 tokens. 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
180-creative-process-structure
description: WHEN approaching design-intensive tasks APPLY structured creative processes globs: ["/.md", "/.mdc"] alwaysApply: true.
190-evaluation-metrics-system
description: WHEN evaluating design solutions APPLY standardized metrics for objective assessment globs: ["/.md", "/.mdc"] alwaysApply: true.
200-quality-verification-procedures
description: WHEN verifying design quality APPLY systematic procedures for validation globs: ["/.md", "/.mdc"] alwaysApply: true.
210-artifact-management-system
description: WHEN managing design artifacts APPLY structured processes for organization and preservation globs: ["/.md", "/.mdc"] alwaysApply: true.
160-workflow-orchestration
WHEN executing tasks MANAGE workflow processes for consistent memory operations.
170-protocol-enforcement-mechanisms
description: WHEN executing commands ENFORCE protocol compliance for memory bank operations globs: ["/.md", "/.mdc"] alwaysApply: true.