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/bernierllc/agents-environment-configWrote 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/bernierllc/agents-environment-config/sqlalchemy)<a href="https://agentmods.dev/rules/bernierllc/agents-environment-config/sqlalchemy"><img src="https://agentmods.dev/badge/rules/bernierllc/agents-environment-config/sqlalchemy/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/bernierllc/agents-environment-config/sqlalchemy"><img src="https://agentmods.dev/badge/rules/bernierllc/agents-environment-config/sqlalchemy.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.00613 |
| Opus 5.5 | $0.00000 | $0.00245 |
| Sonnet 5.5 | $0.00000 | $0.00123 |
| Haiku 4.5 | $0.00000 | $0.00061 |
Grade A, and why
sqlalchemy 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SQLAlchemy Patterns
Naming Conventions
Tables and Models
- snake_case for tables - Use snake_case for table names
- Singular model classes - Model class names should be singular
# ✅ Good
class User(Base):
__tablename__ = "users"
# ✅ Good
class Event(Base):
__tablename__ = "events"
Primary Keys
UUID Primary Keys
- Use UUID(as_uuid=True) PKs - Use UUID primary keys with proper type handling
from sqlalchemy import Column, String
from sqlalchemy.dialects.postgresql import UUID
import uuid
class User(Base):
__tablename__ = "users"
id = Column(
UUID(as_uuid=True),
primary_key=True,
default=uuid.uuid4,
nullable=False
)
Soft Delete Pattern
Deleted At Timestamp
- Use soft-delete pattern via
deleted_at- Don't hard delete records
from sqlalchemy import Column, DateTime
from datetime import datetime
class User(Base):
__tablename__ = "users"
id = Column(UUID(as_uuid=True), primary_key=True)
deleted_at = Column(DateTime, nullable=True)
@property
def is_deleted(self) -> bool:
return self.deleted_at is not None
def soft_delete(self):
self.deleted_at = datetime.utcnow()
Alembic Migrations
Migration Management
- Alembic revision every PR - Create migrations for each pull request
- Never auto-generate without review - Always review generated migrations
- Manual migration review ensures correctness
# Create migration
alembic revision --autogenerate -m "description"
# Review the generated migration file
# Then apply
alembic upgrade head
Migration Best Practices
- Review all auto-generated migrations
- Test migrations on development database first
- Keep migrations small and focused
- Never edit existing migrations (create new ones)
Database Connection
Connection Management
- Use connection pooling
- Proper session management
- Handle connection errors gracefully
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 · 116 lines · 0 tokens per session scan A 82cf61b94e87
sqlalchemy is a cursor rule published in the GitHub repository bernierllc/agents-environment-config (11 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 613 tokens. 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.
Other cursor rules, from other repositories
no-bare-casts
No bare as casts in production TypeScript. Use blindCast (value) from @internal/utils/casts as the auditable escape hatch, castAs (value) for declarative-only assertions, or rewrite to eliminate the cast. as const is exempt. Test files are exempt.
use-ast-factories
Use factory functions for creating AST nodes instead of manual object creation.
sql-types-imports
Canonical import paths for SQL types.
type-extraction-from-contract
Extract TypeScript types from contract.d.ts and helpers.
required-key-undefined-fields
Internal input types use required keys typed | undefined, not optional keys.
type-predicates
Replace blind casts with type predicates (type guards).