trove-python

A set of coding rules for Python and FastAPI, a Python framework for building web APIs. It covers type hints, asynchronous code, database access with SQLAlchemy, data validation with Pydantic, logging, and error handling.

In plain words
What is it for?
Use it when writing or editing Python and FastAPI files, especially API schemas, asynchronous HTTP calls, database code, and error-handling paths.
Why use it?
It gives Python projects consistent conventions and helps prevent problems such as blocking an asynchronous application or leaving function inputs and outputs unclear.

Cursor rule

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/bravew/trove/trove-python
Clone the repo
git clone --depth 1 https://github.com/bravew/trove
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 803 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00000 $0.00803
Opus 5 $0.00000 $0.00402
Sonnet 5 $0.00000 $0.00161
Haiku 4.5 $0.00000 $0.00080

Measured 2d ago against content hash 5711a1ef73e7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

trove-python scanned grade A with 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

response = requests.get(f"/users/{user_id}") # BLOCKING!
plugins/trove-dev/rules/trove-python.mdc · 106 lines

How it starts

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

Trove · v2026.7.4

Session Init

This skill ships Trove conventions. Prefer existing project patterns over generic best practices when they conflict.

Python / FastAPI Conventions

Imports

  • Top-level imports only — never inline imports inside functions
  • Organization: stdlib → third-party → local (isort-compatible)
  • Use from __future__ import annotations when needed for forward refs

Type Hints

  • All function signatures must have type hints (params + return)
  • Use from typing import for complex types (Optional, Union, etc.)
  • Pydantic models for all request/response schemas
  • Prefer X | None over Optional[X] (Python 3.10+)

Async Patterns (CRITICAL)

Never call blocking I/O in async functions:

# BAD — blocks the event loop
async def get_user(user_id: str):
    response = requests.get(f"/users/{user_id}")  # BLOCKING!
    time.sleep(1)  # BLOCKING!

# GOOD — non-blocking
async def get_user(user_id: str):
    async with httpx.AsyncClient() as client:
        response = await client.get(f"/users/{user_id}")
    await asyncio.sleep(1)
  • Use httpx.AsyncClient for HTTP (not requests)
  • Use asyncio.sleep for delays (not time.sleep)
  • Use async with for context managers (DB sessions, HTTP clients)

Logging

# INFO/DEBUG — f-strings are fine (fast path, no Sentry indexing needed)
logger.info(f"Processing user {user_id}")

# WARNING/ERROR — static message + extra dict (enables Sentry grouping)
logger.warning("Payment failed", extra={"user_id": user_id, "amount": amount})

# EXCEPTION — use in except blocks (auto-captures stack trace)
try:
    await process()
except Exception:
    logger.exception("Processing failed", extra={"user_id": user_id})

Never use sentry_sdk.capture_exception() — use logger.exception() instead.

SQLAlchemy Async

# Always use async session context manager
async with get_async_session() as session:
    result = await session.execute(select(User).where(User.id == user_id))
    user = result.scalar_one_or_none()

# Eager loading to avoid N+1
stmt = select(User).options(selectinload(User.posts)).where(User.id == user_id)

Read the full file on GitHub · 106 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. 2d ago First seen · 106 lines · 803 tokens per session scan A 5711a1ef73e7

Subscribe to this mod's changes

trove-python is a cursor rule published in the GitHub repository bravew/trove (10 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 803 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.