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.
npx agentmods add rules/eliornl/rolemule/database-patternsgit clone --depth 1 https://github.com/eliornl/rolemuleWhat 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 | $0.00000 | $0.02957 |
| Opus 5 | $0.00000 | $0.01478 |
| Sonnet 5 | $0.00000 | $0.00591 |
| Haiku 4.5 | $0.00000 | $0.00296 |
Grade A, and why
database-patterns 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 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.
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 — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Database Patterns
Soft Delete on job_applications
The JobApplication model uses soft-delete via deleted_at (nullable DateTime). Always filter it in queries:
# ✅ Always filter soft-deleted records
select(JobApplication).where(
and_(JobApplication.user_id == user_id, JobApplication.deleted_at.is_(None))
)
# Delete = set timestamp, never hard DELETE
application.deleted_at = datetime.now(timezone.utc)
await db.commit()
User.is_admin Field
users.is_admin (Boolean, default False). Check before allowing admin-only operations:
if not current_user.get("is_admin"):
raise forbidden_error("Admin access required")
JSONB Fields — Always flag_modified()
SQLAlchemy cannot detect in-place mutations to JSONB columns. Call flag_modified() for every JSONB field update before commit():
from sqlalchemy.orm.attributes import flag_modified
user_profile.skills = new_skills
flag_modified(user_profile, "skills")
await db.commit()
JSONB columns in this codebase:
UserProfile:work_experience,education,skills,job_types,work_arrangements,desired_salary_range,desired_company_sizes
UserProfile — Field Reference
The UserProfile model contains exactly these fields. There is no location_preferences or target_role field.
| Field | Type | Notes |
|---|---|---|
professional_title |
String | Current job title |
years_experience |
Integer | Total career years; 0 is valid (BasicInfo ge=0). Dashboard JS must not treat 0 as “empty” (see frontend-js-strict.mdc, “Required numeric fields”). |
summary |
Text | Professional summary, 3–4 sentences |
city |
String(100) | Optional location |
state |
String(100) | Optional |
country |
String(100) | Optional |
work_experience |
JSONB | List of past roles with title, company, dates, accomplishments (see completion semantics below) |
education |
JSONB | List of school/program entries: institution, degree, optional field_of_study, dates, is_current (see education completion below) |
skills |
JSONB | List of skill strings |
job_types |
JSONB | e.g. ["full-time", "contract"] |
work_arrangements |
JSONB | e.g. ["remote", "hybrid"] |
desired_salary_range |
JSONB | {min, max} |
desired_company_sizes |
JSONB | e.g. ["startup", "medium"] |
is_student |
Boolean | |
willing_to_relocate |
Boolean | default False |
requires_visa_sponsorship |
Boolean | default False |
work_authorization |
String(64) nullable | no_work_authorization | has_work_authorization | us_lawful_permanent_resident | us_citizen; required for profile completion and extension autofill screening |
has_security_clearance |
Boolean | default False |
max_travel_preference |
String | Optional travel % or category |
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.
- 2d ago First seen · 273 lines · 0 tokens per session scan A 361c5230b9c7
database-patterns is a cursor rule published in the GitHub repository eliornl/rolemule (37 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,957 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-30.
Other cursor rules, from other repositories
cursorrules
Agent2 is a framework for building production AI agents with typed HTTP APIs. PydanticAI handles the agent loop. Agent2 handles everything else: API, auth, pause/resume, approvals, provider routing, knowledge search.
product-manager
Holistic product leader who owns the full product lifecycle — from discovery and strategy through roadmap, stakeholder alignment, go-to-market, and outcome measurement. Bridges business goals, user needs, and technical reality to ship the right thing at the right time.
api-tester
Expert API testing specialist focused on comprehensive API validation, performance testing, and quality assurance across all systems and third-party integrations.
developer-advocate
Expert developer advocate specializing in building developer communities, creating compelling technical content, optimizing developer experience (DX), and driving platform adoption through authentic engineering engagement. Bridges product and engineering teams with external developers.
architectural-and-structural-rules
The project follows a layered architecture with clear separation of concerns.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.