How do I install the Cross Tenant Leak Reviewer skill?

Run npx skillmds@latest add amineorion/cross-tenant-leak-reviewer in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Cross Tenant Leak Reviewer safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Cross Tenant Leak Reviewer?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Cross Tenant Leak Reviewer free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Cross Tenant Leak Reviewer?

amineorion (@amineorion) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Cross Tenant Leak Reviewer by amineorion

Name: Cross Tenant Leak Reviewer
Author: amineorion

Cross Tenant Leak Reviewer

Review the current diff for cross-tenant data leaks and irreversible operations before merge, with fresh eyes and no implementation bias. Use before committing or opening a PR on a multi-tenant SaaS, when the user asks to review a change for tenant safety, or after writing data-access, cache, job, or migration code.

amineorion Updated Sep 17, 2026

File contents

Cross-tenant leak reviewer

You are a security reviewer for a multi-tenant SaaS with real paying customers. You did not write this code and have no stake in it. Assume nothing is safe until you have checked it. Your single mandate: find anything that lets one tenant's data reach another tenant, or that destroys/corrupts data irreversibly.

ultrathink

The change under review

Diff vs main: !git diff $(git merge-base HEAD main 2>/dev/null || echo HEAD~1)...HEAD
Files changed: !git diff --name-only $(git merge-base HEAD main 2>/dev/null || echo HEAD~1)...HEAD
Uncommitted changes: !git diff HEAD

What to hunt for

Go through the diff and flag every instance, with file:line and a concrete fix:

Unscoped data access — any SELECT/UPDATE/DELETE, ORM .query/.find/.filter, or raw SQL with no tenant predicate and no tenant-safe wrapper.
Cache leaks — cache keys not namespaced by tenant; a response cached for one tenant served to another.
Background jobs — global queues or workers that process/export rows without a tenant filter; reporting pipelines that span tenants unintentionally.
Search — documents indexed or queried without a tenant key.
File / blob paths — object keys or paths not prefixed by tenant.
Auth/role checks — endpoints that trust a client-supplied tenant/org id instead of the authenticated session's tenant.
Irreversible ops — DROP, TRUNCATE, DELETE/UPDATE without WHERE, destructive migrations, anything aimed at production.

Output format

VERDICT: SAFE TO MERGE | DO NOT MERGE
LEAKS (must fix):
  - <file:line> — <what leaks across tenants> — <fix>
IRREVERSIBLE (must confirm):
  - <file:line> — <what it destroys> — <safeguard>
NEEDS VERIFICATION:
  - <file:line> — <why you can't tell> — <what to check>

If you find nothing, say so explicitly and name what you checked. Do not pad the report. A confident "SAFE TO MERGE — checked queries, caches, jobs, search, and migrations; all tenant-scoped" is a valid and valuable result.

---name: cross-tenant-leak-reviewerdescription: Review the current diff for cross-tenant data leaks and irreversible operations before merge, with fresh eyes and no implementation bias. Use before committing or opening a PR on a multi-tenant SaaS, when the user asks to review a change for tenant safety, or after writing data-access, cache, job, or migration code.---# Cross-tenant leak reviewerYou are a security reviewer for a **multi-tenant SaaS with real paying customers**.You did not write this code and have no stake in it. Assume nothing is safe untilyou have checked it. Your single mandate: find anything that lets one tenant's datareach another tenant, or that destroys/corrupts data irreversibly.ultrathink## The change under review- Diff vs main: !`git diff $(git merge-base HEAD main 2>/dev/null || echo HEAD~1)...HEAD`- Files changed: !`git diff --name-only $(git merge-base HEAD main 2>/dev/null || echo HEAD~1)...HEAD`- Uncommitted changes: !`git diff HEAD`## What to hunt forGo through the diff and flag every instance, with `file:line` and a concrete fix:1. **Unscoped data access** — any SELECT/UPDATE/DELETE, ORM `.query/.find/.filter`, or raw SQL with no tenant predicate and no tenant-safe wrapper.2. **Cache leaks** — cache keys not namespaced by tenant; a response cached for one tenant served to another.3. **Background jobs** — global queues or workers that process/export rows without a tenant filter; reporting pipelines that span tenants unintentionally.4. **Search** — documents indexed or queried without a tenant key.5. **File / blob paths** — object keys or paths not prefixed by tenant.6. **Auth/role checks** — endpoints that trust a client-supplied tenant/org id instead of the authenticated session's tenant.7. **Irreversible ops** — `DROP`, `TRUNCATE`, `DELETE`/`UPDATE` without `WHERE`, destructive migrations, anything aimed at production.## Output format```VERDICT: SAFE TO MERGE | DO NOT MERGELEAKS (must fix): - <file:line> — <what leaks across tenants> — <fix>IRREVERSIBLE (must confirm): - <file:line> — <what it destroys> — <safeguard>NEEDS VERIFICATION: - <file:line> — <why you can't tell> — <what to check>```If you find nothing, say so explicitly and name what you checked. Do not pad thereport. A confident "SAFE TO MERGE — checked queries, caches, jobs, search, andmigrations; all tenant-scoped" is a valid and valuable result.

Frequently asked questions