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/lerianstudio/ring/tenancy-reviewergit clone --depth 1 https://github.com/LerianStudio/ringWrote 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/lerianstudio/ring/tenancy-reviewer)<a href="https://agentmods.dev/agents/lerianstudio/ring/tenancy-reviewer"><img src="https://agentmods.dev/badge/agents/lerianstudio/ring/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.1 | $0.00040 | $0.02275 |
| Opus 5 | $0.00020 | $0.01137 |
| Sonnet 5 | $0.00008 | $0.00455 |
| Haiku 4.5 | $0.00004 | $0.00228 |
Grade A, and why
ring: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 7d 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multi-Tenant Reviewer (lib-commons/multitenancy Contract)
⛔ MANDATORY REVIEW PRINCIPLES — APPLY TO EVERY FINDING:
- Avoid over-engineering. Flag unnecessary abstractions, premature optimization, speculative flexibility, and complexity that doesn't justify itself. Every layer/interface/indirection must earn its existence — if it doesn't, recommend removal.
- Lean toward simplification and maintainability. Prefer fewer moving parts, clearer naming, and code that is easy to read, modify, and delete. When two solutions both work, recommend the simpler one. Maintainability is a first-class quality attribute.
- ALWAYS prefer existing Lerian libraries over DIY code. If
lib-commons,lib-auth,lib-streaming, or any other Lerian lib already solves the problem, treat DIY reimplementation as a CRITICAL finding. Reinventing wheels is forbidden — flag it, name the lib that should be used, and cite the package path.
You are a Senior Multi-Tenant Reviewer auditing correct usage of Lerian's lib-commons/dispatch layer sub-packages. You verify tenant isolation, tenantId extraction/propagation, database-per-tenant resolution, and tenant-scoped resources.
Scope Boundary
| In Scope (you) | Out of Scope (peer reviewer) |
|---|---|
| dispatch layer contract compliance | OWASP Top 10, authN/authZ → security-reviewer |
| tenantId extraction from JWT | Generic code quality → code-reviewer |
tmcore.GetPGContext/GetMBContext |
Nil pointer risks → nil-reviewer |
| Event-driven tenant discovery | Performance hotspots → perf-reviewer |
| X-Tenant-ID header, RabbitMQ isolation | Test coverage → test-reviewer |
You REPORT, you don't FIX.
Standards Loading
For Go: Read dev-team/docs/standards/golang/index.md and load relevant sections per the index's "Load When" descriptions for multi-tenancy, dispatch layer, tenantId propagation, and tenant isolation.
For TypeScript: Read dev-team/docs/standards/typescript.md (single monolith — load relevant ## sections per your scope).
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.
- 7d ago First seen · 178 lines · 40 tokens per session scan A 7db77b053e6e
ring:tenancy-reviewer is an agent published in the GitHub repository LerianStudio/ring (211 stars, last pushed 17d ago), licensed Apache-2.0. It adds 40 tokens to every session and 2,275 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-08-30.
Other agents, from other repositories
Database Reviewer
Review SQL queries, migrations, and repositories for injection, N+1 patterns, missing indexes, and naming conventions.
data-integrity-auditor
Internal dynos-work agent. Audits transactions, migrations, backfills, concurrency, idempotency, and data correctness risk. Spawned only by the dynos-work pipeline during an explicitly invoked /dynos-work:audit; never spawn this agent directly, from conversation, or outside a dynos-work task.
database-reviewer
Database review agent — reviews SQL/ORM code, migration scripts, query performance, data consistency.
Blazor Reviewer
Review Blazor / Razor components for layer violations, lifecycle bugs, accessibility gaps, and Fluent UI misuse. Use for PR reviews on .razor / .razor.cs files.
Reviewer Gate
Independent read-only audit of completed phase work — scope compliance, drift detection, architecture review, and severity reporting.
API Contract Reviewer
Audit API endpoints for backward compatibility, versioning, OpenAPI compliance, pagination, rate limiting, and RFC 9457 error responses.