cursorrules

A set of coding rules for Python APIs built with FastAPI, Pydantic 2, and SQLAlchemy 2. It defines the project layout, coding conventions, testing tools, and type-hint style.

In plain words
What is it for?
Use it when creating or changing a typed, asynchronous FastAPI service with database models, API routes, business logic, tests, and dependency management.
Why use it?
It gives an agent consistent guidance for structuring and writing this kind of backend, reducing mixed conventions and outdated library syntax.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/setmpp/awesome-cursor-rules-2026/cursorrules
Clone the repo
git clone --depth 1 https://github.com/setmpp/awesome-cursor-rules-2026

Made for: Cursor.

Per session 758 This file is loaded in full into every session.
When invoked 758 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00758 $0.00758
Opus 5 $0.00379 $0.00379
Sonnet 5 $0.00152 $0.00152
Haiku 4.5 $0.00076 $0.00076

Measured yesterday against content hash 547b2a1cd833, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

profiles/python-fastapi/.cursorrules · 98 lines

How it starts

The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.

FastAPI + Pydantic v2 + SQLAlchemy 2

Stack

  • Python 3.12+
  • FastAPI (latest)
  • Pydantic v2 (no v1 syntax)
  • SQLAlchemy 2.0 (new declarative + async)
  • pytest + pytest-asyncio + httpx
  • ruff for lint+format
  • uv for dependency management

Project structure

src/
  app/
    main.py           # FastAPI app factory
    config.py         # Settings via pydantic-settings
    deps.py           # Dependencies (db session, current user)
    api/
      v1/
        routers/      # Each domain = one router file
        schemas/      # Pydantic request/response models
    models/           # SQLAlchemy ORM models
    services/         # Business logic, no FastAPI imports
    repositories/     # DB access, no business logic
    db/
      base.py
      session.py
tests/
  unit/
  integration/

Conventions

Type hints

  • Always type all function signatures.
  • Use X | None not Optional[X]. Use list[X] not List[X].
  • Pydantic model_config = ConfigDict(from_attributes=True) for ORM mapping.

FastAPI routes

  • One router per resource. Mount at /api/v1/<resource>.
  • Use Annotated[Type, Depends(...)] for dependencies.
  • Response models always declared explicitly: response_model=UserOut.
  • 4xx errors via HTTPException. 5xx — let propagate, log in middleware.

Database

  • Async only: AsyncSession, select(...), await session.execute(...).
  • One unit of work per request via dependency.
  • No raw SQL unless ORM can't express it.
  • Migrations: alembic, autogenerate, review every diff.

Validation

  • Pydantic at API boundary only. Inside services — dataclasses or plain types.
  • Custom validators with @field_validator.

Errors

  • Custom exception hierarchy: AppErrorNotFound, Conflict, Forbidden.
  • Exception handler middleware converts to JSON with stable error codes.

Tests

  • pytest-asyncio mode = "auto".
  • Integration tests use testcontainers-postgres.
  • Factories with polyfactory for fixtures.
  • Tests named test_<unit>_<scenario>_<expectation>.

Read the full file on GitHub · 98 lines

Changes

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.

  1. yesterday First seen · 98 lines · 758 tokens per session scan A 547b2a1cd833

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository setmpp/awesome-cursor-rules-2026 (0 stars, last pushed 4mo ago), licensed MIT. It adds 758 tokens to every session, about $0.0038 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.