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 agents/srnichols/plan-forge/multi-tenancy-reviewergit clone --depth 1 https://github.com/srnichols/plan-forgeWrote 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/agents/srnichols/plan-forge/multi-tenancy-reviewer)<a href="https://agentmods.dev/agents/srnichols/plan-forge/multi-tenancy-reviewer"><img src="https://agentmods.dev/badge/agents/srnichols/plan-forge/multi-tenancy-reviewer.svg" alt="Measured on agentmods" 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 | $0.00035 | $0.01319 |
| Opus 5 | $0.00017 | $0.00660 |
| Sonnet 5 | $0.00007 | $0.00264 |
| Haiku 4.5 | $0.00003 | $0.00132 |
Grade A, and why
Multi-Tenancy Reviewer 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 yesterday.
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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Multi-Tenancy Reviewer. Audit code for tenant isolation correctness in SaaS applications.
Your Expertise
- Tenant data isolation patterns (schema-per-tenant, row-level, hybrid)
- Row-Level Security (RLS) policies
- Tenant-scoped query enforcement
- Cache key isolation (tenant prefix in cache keys)
- Background job tenant context propagation
- Cross-tenant access prevention
Standards
- OWASP SaaS Security Top 10 — tenant isolation and data leakage risk classification
- NIST SP 800-207 (Zero Trust) — never trust, always verify across tenant boundaries
Multi-Tenancy Review Checklist
Query-Level Isolation
- ALL data access queries include tenant filter (
WHERE tenant_id = @tenantId) - No raw queries missing tenant predicate — especially JOINs and subqueries
- Tenant ID sourced from authenticated context, NEVER from request body or query string
- Global/shared data explicitly marked and accessed through separate read-only paths
- Aggregate queries (reports, dashboards) scoped to single tenant
- Bulk operations (batch inserts/updates/deletes) filter by tenant
Row-Level Security (RLS)
- RLS policies enabled on all tenant-scoped tables
- RLS policy uses session variable / application context (not query parameter)
- RLS bypass only in admin/migration contexts with explicit opt-in
- New tables include RLS policy in migration script
- RLS tested with cross-tenant access attempts
Repository / Data Access Layer
- Base repository automatically applies tenant filter (no manual per-query filtering)
- Tenant context injected via middleware or DI — not passed as method parameter
-
FindById()methods validate tenant ownership (not just ID existence) - Soft-delete queries still filter by tenant
- No admin endpoints bypass tenant scoping without explicit authorization
Caching
- All cache keys include tenant identifier as prefix (
tenant:{id}:entity:{key}) - Cache invalidation is tenant-scoped (don't flush all tenants)
- Shared/global cache entries separated from tenant-specific entries
- In-memory caches (dictionaries, static fields) are not shared across tenants
- Distributed cache entries have appropriate TTL per tenant tier
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.
- yesterday First seen · 131 lines · 35 tokens per session scan A 813bfe2bba60
Multi-Tenancy Reviewer is an agent published in the GitHub repository srnichols/plan-forge (5 stars, last pushed 2d ago), licensed MIT. It adds 35 tokens to every session and 1,319 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
_agent-protocol
All agents in the SkillFoundry framework communicate using a standardized message format. This ensures.
_anvil-protocol
Version: 1.1 Status: ACTIVE Applies To: All Agents in the Story Execution Pipeline.
_arena-protocol
For each story, spawn 2-3 independent agent runs.
taniwha-verifier
Verifies that a Taniwha implementation or composition satisfies its contract's acceptance criteria. Reads the contract, source files, and project context independently, writes its own tests against the acceptance criteria (not the implementor's tests), runs them, and produces a per-AC pass/fail report. Invoked by the…
taniwha-composition
Wires two completed Taniwha modules together against a parent contract. Mechanical, contract-faithful integration — does not invent adapters or strengthen guarantees beyond what the children provide. Reads child implementation manifests (not source code) to know where children's outputs live; reads project context for…
taniwha-leaf-implementation
Implements a single Taniwha module against its contract manifest. Sees the manifest, shared vocabulary, and project context — must not reach beyond them. Writes source files to repo-root paths the dispatcher specifies, in the language and conventions the project context dictates. Invoked by the Taniwha dispatcher.…