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/urule-ai/urule/cursorrulesgit clone --depth 1 https://github.com/urule-ai/uruleWhat 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.00315 | $0.00315 |
| Opus 5 | $0.00158 | $0.00158 |
| Sonnet 5 | $0.00063 | $0.00063 |
| Haiku 4.5 | $0.00032 | $0.00032 |
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
You are working on Urule, the open-source coordination layer for AI agents.
Tech stack: TypeScript ESM, Fastify 5, Drizzle ORM, PostgreSQL 16, NATS, Vitest, Next.js 14, React 18, Tailwind CSS, Zustand.
Rules:
- Always use ESM imports with .js extension for local files
- Use ULID (not UUID) for all IDs: import { ulid } from 'ulid'
- Use Zod for all request body validation with safeParse()
- Return 400 with { error: 'Validation failed', details: parsed.error.issues } on validation failure
- Return 404 with { error: { code: 'ENTITY_NOT_FOUND', message } } for missing resources
- TypeScript strict mode — never use
any, useunknownwith validation - Use Fastify app.inject() for route tests, never start a real server
- Use request.log (Pino) for logging, never console.log in services
- Each service has its own PostgreSQL schema — never cross-query
- Services communicate via HTTP APIs and NATS events — never import between services
- Follow Conventional Commits: feat:, fix:, docs:, test:, refactor:, chore:
- Auth middleware uses skipAuth: true in tests
- Public routes go in the publicRoutes array (healthz, /docs, webhooks)
- All list endpoints support limit/offset pagination (max 100)
See CLAUDE.md for detailed patterns, recipes, and architecture.
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 · 22 lines · 315 tokens per session scan A 49a6cb431ff7
cursorrules is a cursor rule published in the GitHub repository urule-ai/urule (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 315 tokens to every session, about $0.0016 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-31.
Other cursor rules, from other repositories
integration-issue-conventions
When creating or editing SuperPlane integration issue content (base or component issues), or when working in tmp/integrationspm or integration PM workflow.
rules-index
Opptrix 规则路由引擎 — 唯一常驻层;每任务开始前必先规划规则加载.
index
CodeGraph 本地索引说明 — 运行态在仓库 .codegraph/(gitignore),模板在 /.projects-rules/Opptrix/.
planning
Complete feature development lifecycle using memory-backed planning. Creates requirements, design, and task memories. Use when: starting new features, planning implementations, organizing development work, managing project specifications.
frontend
This rule provides comprehensive guidance for front-end development in Igniter.js + Next.js + Shadcn UI projects, ensuring consistent architecture, component patterns, and seamless integration with existing workflows.
rules
Establishes a comprehensive framework for Lia's autonomous self-improvement, ensuring continuous evolution of her training system while maintaining accuracy and preventing hallucinations.