PatrickJS/awesome-cursorrules is a collection of Markdown rule files that give Cursor AI editor project-specific instructions about code, frameworks, workflows, and standards. Developers use it to find reusable guidance for shaping Cursor’s behavior in different kinds of software projects.
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/patrickjs/awesome-cursorrules/sveltekit-restful-api-tailwind-css-cursorrules-progit clone --depth 1 https://github.com/PatrickJS/awesome-cursorrulesWrote 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/patrickjs/awesome-cursorrules/sveltekit-restful-api-tailwind-css-cursorrules-pro)<a href="https://agentmods.dev/rules/patrickjs/awesome-cursorrules/sveltekit-restful-api-tailwind-css-cursorrules-pro"><img src="https://agentmods.dev/badge/rules/patrickjs/awesome-cursorrules/sveltekit-restful-api-tailwind-css-cursorrules-pro.svg" alt="Measured on agentmods" 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.00793 | $0.00793 |
| Opus 5 | $0.00396 | $0.00396 |
| Sonnet 5 | $0.00159 | $0.00159 |
| Haiku 4.5 | $0.00079 | $0.00079 |
Grade A, and why
sveltekit-restful-api-tailwind-css-cursorrules-pro 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 2d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
File Path Usage
IMPORTANT: Always use full file paths when referencing, editing, or creating files.
Example: E:\Stojanovic-One\src\routes\Home.svelte
This rule applies to all file operations and must be followed consistently.
You are an AI assistant for the Stojanovic-One web application project. Adhere to these guidelines:
Please this is utterly important provide full file paths for each file you edit, create or delete. Always provide it in a format like this: edit this file now: E:\Stojanovic-One\src\routes\Home.svelte or create this file in this path: E:\Stojanovic-One\src\routes\Home.svelte Also always provide file paths as outlined in @AI.MD like if you say lets update this file or lets create this file always provide the paths.
- Tech Stack:
- Frontend & Backend: SvelteKit
- Database: PostgreSQL (via Supabase)
- UI Styling: Tailwind CSS
- Deployment: Vercel
- Authentication: Supabase Auth
-
Follow Elon Musk's Algorithm for Efficiency: a. Question every requirement critically b. Delete unnecessary parts c. Simplify and optimize remaining components d. Accelerate cycle time e. Automate as the final step
-
Practice Test-Driven Development (TDD):
- Write failing tests first
- Implement minimum code to pass tests
- Refactor while maintaining passing tests
- File Management:
- Include full file path as a comment at the start of each file
- Update project structure in AI.MD when adding new files/directories
- Maintain up-to-date package.json
- Testing:
- Use Vitest for unit and integration tests
- Aim for high test coverage (80% or higher)
- Code Quality:
- Prioritize readability and maintainability
- Implement comprehensive error handling
- Use TypeScript for type safety
- Documentation:
- Write clear comments and use JSDoc when appropriate
- Keep README.md and AI.MD updated
- Maintain CHANGELOG.md for significant changes
- Truthfulness and Clarity:
- Provide accurate, thoughtful answers
- Admit when you don't know something
- Be concise while ensuring clarity
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.
- 2d ago First seen · 94 lines · 793 tokens per session scan A 39fe0d69fc89
sveltekit-restful-api-tailwind-css-cursorrules-pro is a cursor rule published in the GitHub repository PatrickJS/awesome-cursorrules (40,728 stars, last pushed 3mo ago), licensed CC0-1.0. It adds 793 tokens to every session, about $0.0040 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-09-03.
Other cursor rules, from other repositories
vue3-typescript-auto
Vue 3 with TypeScript Standards.
vue-test-utils-auto
@vue/test-utils Standards for Vue 3 components and Vitest.
vue
Vue 3: Composition API, Pinia, script setup.
nuxt
Nuxt 3: composables, server routes, auto-imports.
sveltekit
SvelteKit: load functions, form actions, +page/+layout patterns.
svelte
Svelte 5: runes, reactivity, stores.