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.
git 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/python-fastapi-scalable-api-cursorrules-prompt-fil)<a href="https://agentmods.dev/rules/patrickjs/awesome-cursorrules/python-fastapi-scalable-api-cursorrules-prompt-fil"><img src="https://agentmods.dev/badge/rules/patrickjs/awesome-cursorrules/python-fastapi-scalable-api-cursorrules-prompt-fil/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/patrickjs/awesome-cursorrules/python-fastapi-scalable-api-cursorrules-prompt-fil"><img src="https://agentmods.dev/badge/rules/patrickjs/awesome-cursorrules/python-fastapi-scalable-api-cursorrules-prompt-fil.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.01063 | $0.01063 |
| Opus 5.5 | $0.00425 | $0.00425 |
| Sonnet 5.5 | $0.00213 | $0.00213 |
| Haiku 4.5 | $0.00106 | $0.00106 |
Grade A, and why
python-fastapi-scalable-api-cursorrules-prompt-fil 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.
How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert in Python, FastAPI, scalable API development, TypeScript, React, Tailwind, and Shadcn UI.
Key Principles
- Write concise, technical responses with accurate examples in both Python and TypeScript.
- Use functional and declarative programming patterns; avoid classes unless absolutely necessary.
- Prefer iteration and modularization over code duplication.
- Use descriptive variable names with auxiliary verbs (e.g.,
is_active,has_permission,isLoading,hasError). - Follow proper naming conventions:
- For Python: use lowercase with underscores (e.g.,
routers/user_routes.py). - For TypeScript: use lowercase with dashes for directories (e.g.,
components/auth-wizard).
- For Python: use lowercase with underscores (e.g.,
Project Structure
-
Frontend:
- Language: TypeScript
- Framework: React
- UI Library: Tailwind CSS, Shadcn UI
- Build Tool: Vite
- Directory Structure:
frontend/src/: Main source codefrontend/src/index.html: Main HTML file- Configuration Files:
vite.config.tstsconfig.jsontailwind.config.jspostcss.config.js
- Docker Files:
DockerfileDockerfile.dev
-
Backend:
- Language: Python
- Framework: FastAPI
- Database: PostgreSQL
- Directory Structure:
backend/src/: Main source codebackend/tests/: Testsdocument-processor/: Document processing utilities- Environment Configuration:
.env/.env.example: Environment variables
- Database Configuration:
alembic.iniddialog.db: SQLite database for local development
- Docker Files:
DockerfileDockerfile.dev
Code Style and Structure
Backend (Python/FastAPI):
- Use
deffor pure functions andasync deffor asynchronous operations. - Type Hints: Use Python type hints for all function signatures. Prefer Pydantic models for input validation.
- File Structure: Follow clear separation with directories for routes, utilities, static content, and models/schemas.
- RORO Pattern: Use the "Receive an Object, Return an Object" pattern.
- Error Handling:
- Handle errors at the beginning of functions with early returns.
- Use guard clauses and avoid deeply nested if statements.
- Implement proper logging and custom error types.
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 · 110 lines · 1,063 tokens per session scan A f5ce7070822e
python-fastapi-scalable-api-cursorrules-prompt-fil is a cursor rule published in the GitHub repository PatrickJS/awesome-cursorrules (40,986 stars, last pushed 4mo ago), licensed CC0-1.0. It adds 1,063 tokens to every session, about $0.0043 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-09-03.
Other cursor rules, from other repositories
graphql-apollo-client-usage
A usage guide for fetching, changing, and subscribing to GraphQL data with Apollo Client in React. It covers loading and error states, cache updates, refetching, and reusable GraphQL fragments.
chakra-ui-best-practices
A set of rules for building React interfaces with Chakra UI, a component library for styled and accessible user interfaces. It covers themes, responsive layouts, accessibility, performance, and reusable components.
chakra-ui---responsive-design
Guidance for making Chakra UI layouts adapt to different screen sizes. It uses responsive style values, breakpoints, layout components, and conditional display rules for phones, tablets, and desktops.
chakra-ui---theme-directory-rules
Rules for organizing a Chakra UI theme into an entry file, foundational settings, and component-specific styles. The theme controls shared colors, fonts, spacing, breakpoints, and component variants.
chakra-ui---dark-mode-implementation
A Chakra UI rule for adding a light and dark color mode to React components. It covers switching modes, following the system preference, storing the choice, and preventing a flash of the wrong theme during loading.
react-chakra-ui---folder-structure
A standard folder layout for React and Chakra UI projects, including separate locations for components, pages, themes, hooks, utilities, and assets. It also defines how Chakra UI theme files are grouped.