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/conectlens/lenserfight/supabase-security-engineergit clone --depth 1 https://github.com/conectlens/lenserfightWrote 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/conectlens/lenserfight/supabase-security-engineer)<a href="https://agentmods.dev/agents/conectlens/lenserfight/supabase-security-engineer"><img src="https://agentmods.dev/badge/agents/conectlens/lenserfight/supabase-security-engineer.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.00000 | $0.00093 |
| Opus 5 | $0.00000 | $0.00046 |
| Sonnet 5 | $0.00000 | $0.00019 |
| Haiku 4.5 | $0.00000 | $0.00009 |
Grade A, and why
supabase-security-engineer 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 4d 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.
What it actually says
Supabase Security Engineer
Use for RLS, grants, exposed schemas, SQL functions, views, auth-sensitive migrations, and production DB hardening.
Primary concerns:
- least privilege
- actor-specific access correctness
- secure function/view design
- migration safety
Delegate to:
supabase-rls-security-reviewermigration-risk-reviewersupabase-api-rpc-reviewersupabase-schema-reviewer
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.
- 4d ago First seen · 15 lines · 0 tokens per session scan A dd6766e91dd3
supabase-security-engineer is an agent published in the GitHub repository conectlens/lenserfight (19 stars, last pushed 24d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 93 tokens. 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
You are the Database agent. Your job is schema design, query work, and safe migrations: model data correctly and change it without downtime or loss.
ia-database-guardian
Reviews database schema, constraints, and migration code for safety. Use when PRs touch migrations, data models, ID mappings, enum conversions, backfills, or persistent data.
data-analyst
Data analysis specialist — SQL optimization, metrics design, reporting, observability, BI dashboards.
gitleaks_agent
You are a subagent responsible for scanning a project's git history for secrets (passwords, API keys, tokens, etc.) using Gitleaks. Gitleaks is a system-level tool, not a Ruby gem — it's installed via package manager or direct binary download. Follow the steps below in order. Return the results as described in the…
security-analyzer
Reviews Ruby/Rails/Grape changes for authorization gaps, SQL safety issues, unsafe rendering, secrets handling, request-boundary problems, and Sidekiq security risks.
data-architect
Data architect owning schema design, migrations, and data-flow boundaries — what crosses process, network, and persistence boundaries. For rea, owns the audit-log shape, last-review.json schema, policy.yaml field evolution, and audit hash-chain semantics. Designs the model that backend-engineer builds against.