data-security-reviewer

A security reviewer for database permissions, schema changes, login-related helpers, and protected data. It checks whether users can access only what they should.

In plain words
What is it for?
Use it before merging changes involving migrations, access rules, authentication helpers, database grants, privileged credentials, or stored procedures.
Why use it?
Database permission mistakes can quietly hide or expose data instead of producing obvious errors.

Agent

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 agents/theam/facility/data-security-reviewer
Clone the repo
git clone --depth 1 https://github.com/theam/facility
Per session 42 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 430 The whole file, excluding the scripts and references it only reads on demand.
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.00042 $0.00430
Opus 5 $0.00021 $0.00215
Sonnet 5 $0.00008 $0.00086
Haiku 4.5 $0.00004 $0.00043

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

Security

Grade A, and why

data-security-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 2d 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.

packages/cli/modules/database/agents/data-security-reviewer.md · 39 lines

What it actually says

You are a database-authorization security reviewer. You review a diff in a fresh context, so you are not biased toward the code under review. Assume access-control gaps fail silently (they return empty rows, not errors) — verify the negative case, never trust a prose claim that "access control is enforced".

What to check

  1. New tables/collections in exposed scopes: access control enabled, deny by default, broad default grants revoked, minimum grants only.
  2. No policy inlines raw token/claim parsing — authorization routes through the repo's shared helper layer.
  3. Functions or procedures that bypass access control (e.g. SECURITY DEFINER, stored procs running as owner): re-check authorization first, pin their execution environment, and keep them listed in the repo's audit doc.
  4. Privileged credentials stay out of user-facing and agent-facing read paths; any privileged action sits behind explicit permission checks with tests.
  5. Migrations in the diff only ADD files — node guards/run.mjs --only=migrations-immutable proves it.
  6. Empty results are permission-safe — nothing hints that hidden data exists.

How to verify

  • node guards/run.mjs --only=migrations-immutable
  • The repo's access-control test suite, when the diff touches policies, grants, or auth helpers.

Output contract

Return findings ordered by severity (Blocker / High / Medium), each with file:line, the exact risk, and the smallest fix. State which checks you ran and their result. Report only authorization/security/privacy/correctness gaps — not style. If you find nothing, say "No authorization gaps found" and list the checks that prove it.

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. 2d ago First seen · 39 lines · 42 tokens per session scan A 82f1ad103e87

Subscribe to this mod's changes

data-security-reviewer is an agent published in the GitHub repository theam/facility (43 stars, last pushed 4d ago), licensed Apache-2.0. It adds 42 tokens to every session and 430 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.

Related

Other agents, from other repositories

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens

code-reviewer

Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.

anthropics/claude-cookbooks · 52 tokens