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/bravew/troveWrote 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/bravew/trove/trove-python)<a href="https://agentmods.dev/rules/bravew/trove/trove-python"><img src="https://agentmods.dev/badge/rules/bravew/trove/trove-python/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/bravew/trove/trove-python"><img src="https://agentmods.dev/badge/rules/bravew/trove/trove-python.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.00791 | $0.00791 |
| Opus 5.5 | $0.00316 | $0.00316 |
| Sonnet 5.5 | $0.00158 | $0.00158 |
| Haiku 4.5 | $0.00079 | $0.00079 |
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 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.
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! How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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 annotationswhen needed for forward refs
Type Hints
- All function signatures must have type hints (params + return)
- Use
from typing importfor complex types (Optional,Union, etc.) - Pydantic models for all request/response schemas
- Prefer
X | NoneoverOptional[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.AsyncClientfor HTTP (notrequests) - Use
asyncio.sleepfor delays (nottime.sleep) - Use
async withfor 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)
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 Changed · -2 lines · -12 tokens per session 86a17106c779
- 1mo ago First seen · 106 lines · 803 tokens per session scan A 5711a1ef73e7
trove-python is a cursor rule published in the GitHub repository bravew/trove (10 stars, last pushed yesterday), licensed MIT. It adds 791 tokens to every session, about $0.0032 per session on Opus 5.5. 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.
Other cursor rules, from other repositories
python_tests
We use the unit tests to cover internal behavior that can work without the web / backend counterpart. We aim for 95%+ unit test coverage of our Python code in lib/streamlit.
django-python
Rules for writing Python services at PostHog (Python servers powered by the Django framework).
py-fast-api
Cursor rules for Python FastAPI backend development and best practices.
python
Python best practices and patterns for modern software development with Flask and SQLite.
python--typescript-guide-cursorrules-prompt-file
Cursor rules for Python development with TypeScript guide integration.
python-conventions
Python coding style, FastAPI endpoint template, code organisation sections.