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 skills add event4u-app/agent-config --skill multi-tenancygit clone --depth 1 https://github.com/event4u-app/agent-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/skills/event4u-app/agent-config/multi-tenancy)<a href="https://agentmods.dev/skills/event4u-app/agent-config/multi-tenancy"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/multi-tenancy/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/skills/event4u-app/agent-config/multi-tenancy"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/multi-tenancy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00032 | $0.01247 |
| Opus 5.5 | $0.00013 | $0.00499 |
| Sonnet 5.5 | $0.00006 | $0.00249 |
| Haiku 4.5 | $0.00003 | $0.00125 |
Grade A, and why
multi-tenancy 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 today.
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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
multi-tenancy
When to use
Use this skill when working with tenant-specific data, customer database connections, or any code that touches the dual-database architecture.
Two tenancy modes exist: database-per-tenant (this body) and shared-schema
(tenant_id in every tenant table: child foreign keys carry tenant_id, the
parent is UNIQUE (tenant_id, id)) — the full key rules are in
references/shared-schema-integrity.md.
Do NOT use when:
- Single-tenant applications (no tenant database, no
tenant_id) - Frontend-only changes
Procedure: Work with multi-tenancy
- Gather context — read
agents/reference/docs/for multi-tenant architecture,config/database.phpfor connection definitions, and search for the tenant switching service. - Identify connection — determine whether the code touches central, tenant, or both databases. Set
$connectionexplicitly on any new model. - Implement — write the feature using the correct connection. Use the tenant switching service for cross-tenant operations. Never mix connections in a single query.
- Verify isolation — inspect the code for tenant leaks: global scopes, missing
$connection, shared caches, or job serialization without tenant context. - Test — write a test that exercises the tenant boundary: seed tenant-specific data, switch context, verify correct data is returned and other tenants' data is invisible.
Architecture overview
Request → Identify Tenant (JWT / subdomain / API key)
→ Lookup credentials from central database
→ Reconfigure tenant connection at runtime
→ All tenant queries use tenant connection
Dual-database pattern
| Connection type | Purpose | Scope |
|---|---|---|
| Central / shared | Global data — tenants, config, shared resources | Shared across all tenants |
| Tenant / customer | Tenant-specific data — domain entities | One per tenant |
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today Changed · +4 lines 4c7a761ddfa6
- 1mo ago First seen · 146 lines · 32 tokens per session scan A c13447c9a214
multi-tenancy is a skill published in the GitHub repository event4u-app/agent-config (16 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 1,247 once invoked, about $0.0001 per session on Opus 5.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-09-04.
Other skills, from other repositories
cqrs-implementation
Implement Command Query Responsibility Segregation for scalable architectures. Use when separating read and write models, optimizing query performance, or building event-sourced systems.
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
supabase-cli
This skill should be used when user asks to "use supabase CLI", "supabase init", "supabase start", "run migrations", "deploy edge functions", "manage Supabase project", or works with the supabase command-line tool for local development and project management.
durable-objects
Build, debug, or review Cloudflare Durable Objects code for persistent state and coordination.
architect/data-api-design
A guide to designing data models and application programming interfaces (APIs), which are the rules software uses to exchange data.
solr-extending
To build Solr plugins: SearchComponent, QParser, URP, DocTransformer.