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 skills add cwinvestments/memstack --skill rls-checkergit clone --depth 1 https://github.com/cwinvestments/memstackWrote 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/skills/cwinvestments/memstack/rls-checker)<a href="https://agentmods.dev/skills/cwinvestments/memstack/rls-checker"><img src="https://agentmods.dev/badge/skills/cwinvestments/memstack/rls-checker/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/cwinvestments/memstack/rls-checker"><img src="https://agentmods.dev/badge/skills/cwinvestments/memstack/rls-checker.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00080 | $0.02818 |
| Opus 5.5 | $0.00032 | $0.01127 |
| Sonnet 5.5 | $0.00016 | $0.00564 |
| Haiku 4.5 | $0.00008 | $0.00282 |
Grade A, and why
memstack-security-rls-checker 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 1mo 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 — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🔒 RLS Checker: Auditing Row Level Security...
Audit Supabase Row Level Security policies across all tables in a project.
Activation
When this skill activates, output:
🔒 RLS Checker: Auditing Row Level Security...
Then execute the protocol below.
Context Guard
| Context | Status |
|---|---|
| User asks to check/audit RLS | ACTIVE: full audit |
| User mentions Supabase security | ACTIVE: full audit |
| User asks about table permissions | ACTIVE: full audit |
| User is writing RLS policies | DORMANT, they know what they're doing |
| Non-Supabase project | DORMANT: not applicable |
Protocol
Step 1: Discover Tables
Find all Supabase tables referenced in the project. Search in priority order:
-
Migration files: most authoritative source:
find . -path "*/migrations/*.sql" -o -path "*/supabase/migrations/*.sql" | head -50Look for
CREATE TABLEstatements. -
Generated types: comprehensive if available:
types/database.ts, types/supabase.ts, src/types/database.types.ts, database.types.tsParse the
Tablesinterface for all table names. -
Client usage: catches tables missed by above:
grep -r "\.from(['\"]" --include="*.ts" --include="*.tsx" --include="*.js"Extract table names from
.from('table_name')calls. -
Storage buckets: separate RLS surface:
grep -r "storage\.from\|createBucket\|storage-api" --include="*.ts" --include="*.tsx" --include="*.sql"
Compile a deduplicated list of all tables and storage buckets.
Step 2: Extract RLS Policies
For each table, find its RLS configuration:
- Search migration SQL for RLS statements:
ALTER TABLE <name> ENABLE ROW LEVEL SECURITY: RLS is onCREATE POLICYstatements: extract policy name, operation (SELECT/INSERT/UPDATE/DELETE/ALL), and USING/WITH CHECK expressionsALTER TABLE <name> FORCE ROW LEVEL SECURITY: RLS enforced even for table owners
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.
- 1mo ago Changed eefd3429253a
- 1mo ago First seen · 271 lines · 80 tokens per session scan A 5e1f4455d6ed
memstack-security-rls-checker is a skill published in the GitHub repository cwinvestments/memstack (425 stars, last pushed yesterday), licensed MIT. It adds 80 tokens to every session and 2,818 once invoked, about $0.0003 per session on Opus 5.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 skills, from other repositories
elasticsearch-best-practices
Elasticsearch development best practices for indexing, querying, and search optimization.
kysely
Guidelines for developing with Kysely, a type-safe TypeScript SQL query builder with autocompletion support.
mysql-best-practices
MySQL development best practices for schema design, query optimization, and database administration.
pyspark-etl
Best practices for building performant, testable PySpark ETL pipelines with Spark SQL and Apache Iceberg. Use when writing or reviewing PySpark jobs, designing joins and window functions, working with map/array higher-order functions, or building idempotent cumulative/snapshot table merges.
drizzle-orm
Guidelines for developing with Drizzle ORM, a lightweight type-safe TypeScript ORM with SQL-like syntax.
postgresql-best-practices
PostgreSQL development best practices for schema design, query optimization, and database administration.