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/bybren-llc/a-safe-pulseWrote 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/bybren-llc/a-safe-pulse/10-backend-python)<a href="https://agentmods.dev/rules/bybren-llc/a-safe-pulse/10-backend-python"><img src="https://agentmods.dev/badge/rules/bybren-llc/a-safe-pulse/10-backend-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/bybren-llc/a-safe-pulse/10-backend-python"><img src="https://agentmods.dev/badge/rules/bybren-llc/a-safe-pulse/10-backend-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.00000 | $0.00610 |
| Opus 5.5 | $0.00000 | $0.00244 |
| Sonnet 5.5 | $0.00000 | $0.00122 |
| Haiku 4.5 | $0.00000 | $0.00061 |
Grade A, and why
10-backend-python 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.
This is a copy
100% identical to 10-backend-python — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend Python Rules
These rules apply when working on backend Python code in core/ and edgekit/.
Technology Stack
- Framework: FastAPI (Python 3.11+)
- ORM: SQLAlchemy 2.x with async session patterns
- Migrations: Alembic
- Database: PostgreSQL 16
- Authentication: JWT (custom implementation)
Coding Standards
- Use
rufffor linting and formatting (config inpyproject.toml) - Always run
ruff check .before committing - Use
mypyfor type checking - Python 3.11+ features are allowed (StrEnum, etc.)
- Use async/await patterns for all FastAPI endpoints
Database Operations
CRITICAL: All database operations MUST use RLS context helpers.
# User operations
async with with_user_context(session, user_id) as ctx:
result = await ctx.execute(select(Model).where(Model.user_id == user_id))
# Admin operations
async with with_admin_context(session, user_id) as ctx:
result = await ctx.execute(select(Model))
# System/background operations
async with with_system_context(session, "source_name") as ctx:
result = await ctx.execute(insert(Model).values(data))
Never use direct session calls without RLS context wrappers.
Migration Workflow
alembic revision --autogenerate -m "description" # Create migration
alembic upgrade head # Apply locally
# Review the generated migration file before committing
git add alembic/versions/
git commit -m "feat(db): add migration description [ASP-XXX]"
Rules:
- Always create proper Alembic migrations (never skip)
- Review auto-generated migrations for correctness
- Add RLS policies for any new tables
- Schema changes require System Architect approval
FastAPI Patterns
- Use dependency injection for database sessions
- Use Pydantic v2 models for request/response validation
- Use proper HTTP status codes
- Include OpenAPI documentation (FastAPI generates this)
- Use structured logging
Testing
- Use
pytestwith async support (pytest-asyncio) - Run
pytest tests/before committing - Integration tests go in
tests/integration/ - E2E tests go in
tests/e2e/
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 · 84 lines · 0 tokens per session scan A 9a0ecf654a3e
10-backend-python is a cursor rule published in the GitHub repository bybren-llc/a-safe-pulse (9 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 610 tokens. A static security scan graded it A with 0 findings. It is 100% identical to 10-backend-python, differing in 2 lines, and is treated as a copy.
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).
020-flask
Flask API Gateway conventions for LMForge.
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.