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/lktiep/cortex-hub/cursorrulesgit clone --depth 1 https://github.com/lktiep/cortex-hubWhat 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.00248 | $0.00248 |
| Opus 5 | $0.00124 | $0.00124 |
| Sonnet 5 | $0.00050 | $0.00050 |
| Haiku 4.5 | $0.00025 | $0.00025 |
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 yesterday.
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
Cortex Hub (MANDATORY)
At the START of every conversation:
cortex_session_startwith repo: "https://github.com/lktiep/cortex-hub.git", agentId: "cursor", mode: "development"- If
recentChanges.count > 0, warn user andgit pull cortex_memory_search+cortex_knowledge_search— recall previous session context
During Work
Use cortex tools before grep/find: code_search → code_impact → code_context. Fall back to grep only if no results.
Error Protocol
cortex_knowledge_searchfirst — someone may have solved this- Fix the error
- Non-obvious fixes:
cortex_knowledge_storeto save the solution
Ending
- Run verify:
pnpm build && pnpm typecheck && pnpm lint cortex_quality_reportwith resultscortex_memory_store— persist session learningscortex_session_endwith sessionId and summary
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.
- yesterday First seen · 23 lines · 248 tokens per session scan A 4881cd7f4736
cursorrules is a cursor rule published in the GitHub repository lktiep/cortex-hub (58 stars, last pushed 1mo ago), licensed MIT. It adds 248 tokens to every session, about $0.0012 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
compat-ui
WWorkbench Compat 平台交互层约定（press / Select / Modal / FocusGate）.
codesynapse-cli
Use this rule to answer codebase architecture questions, trace dependencies, find callers/callees, calculate blast radius, and explore the code graph. Triggers on: "how does X work", "what handles Y", "where is Z defined", "explain the mechanism", "who calls", "blast radius", "shortest path", "trace request flow"…
codesift
CodeSift MCP tool usage rules.
architectural-and-structural-rules
The project follows a layered architecture with clear separation of concerns.
api-design-and-implementation
API Design and Implementation Rules for FastAPI Endpoints.
testing-and-security
Testing and Security Guidelines for FastAPI Applications Including Unit Testing, Environment Variable Management, and Authentication Security.