004-multi-tenancy-pattern

004-multi-tenancy-pattern is a cursor rule for Cursor from phuoctrung-ppt/ai-sdlc-workflow. It costs 378 tokens per session, scanned A, original, MIT.

A soft multi-tenancy pattern keeps multiple customers’ data in one application database while separating access in application code. A tenant is a customer or organization using the application.

In plain words
What is it for?
Use it to guide tenant identifiers, tenant context checks, customer registration, and access rules for shared application data.
Why use it?
It defines which records belong to a customer and requires customer-scoped queries, reducing the risk of cross-customer access.

Cursor rule for Cursor

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/phuoctrung-ppt/ai-sdlc-workflow/004-multi-tenancy-pattern
Clone the repo
git clone --depth 1 https://github.com/phuoctrung-ppt/ai-sdlc-workflow

Made for: Cursor.

Per session 378 This file is loaded in full into every session.
When invoked 378 The same file — it is already loaded in full.
Security scan A 0 findings. 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.00378 $0.00378
Opus 5 $0.00189 $0.00189
Sonnet 5 $0.00076 $0.00076
Haiku 4.5 $0.00038 $0.00038

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

Security

Grade A, and why

004-multi-tenancy-pattern 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 3d 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.

.cursor/rules/004-multi-tenancy-pattern.mdc · 34 lines

What it actually says

Soft Multi-Tenancy (MVP)

⚠️ EXAMPLE DOMAIN (AI hiring/recruiting) — NOT this project's rules. This file is a portable example of a soft multi-tenancy pattern. Its specifics (jobs, applications, interview_recordings, CVs, HR/candidate roles) do not describe the current project. Agents: ignore the domain specifics below until this file is replaced with the real tenancy model for <PROJECT> (see AGENTS.md §4). Delete or rewrite on port.

Details: AGENTS.md §4. Application-level isolation, no RLS in MVP.

tenant_id Rules

  • Has tenant_id: users (nullable), jobs, applications, interview_recordings, audit_logs
  • No tenant_id: cvs, cv_versions, skills, consents (global/candidate-owned)
  • Candidates: tenant_id NULL; HR: tenant_id NOT NULL; Admin users: NULL

Application Isolation

  • TenantContextGuard + @TenantId() on tenant-scoped queries
  • HR queries MUST filter tenant_id; no cross-tenant access on app API
  • Admin service: cross-tenant read-only for analytics

Tenant Lifecycle

  • Auto-create tenant on HR register: plan=free, max_users=5, max_jobs=3, max_ai_credits=100
  • Reject if tenant.status != 'active'; soft limits → 403 with upgrade prompt
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. 3d ago First seen · 34 lines · 378 tokens per session scan A fb2e0f3e497a

Subscribe to this mod's changes

004-multi-tenancy-pattern is a cursor rule published in the GitHub repository phuoctrung-ppt/ai-sdlc-workflow (2 stars, last pushed 17d ago), licensed MIT. It adds 378 tokens to every session, about $0.0019 per session on Opus 5. 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.