Rls security
Reusable, token-optimized agent skills for autonomous development with Hermes, Claude Code & OpenCode. Multi-model orchestration patterns — context-checkpointing, human review gates, RLS security, GDPR consent, AI cost control, and test-fix loops. Framework-agnostic, agentskills.io compatible.
npx -y skills add prasadmogulothu/agent-skills --skill rls-securityAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Generate row-level-security policies plus a cross-user isolation test, so users can only access their own rows. Written for Postgres/Supabase; adaptable to other databases. Use for any per-user or multi-tenant data.
SKILL.md
1.4 KB, as published. Nobody here has run it
rls-security
Make per-user data isolation enforced at the database layer, not just in app code — and prove it.
Do
Given a table spec:
- Create the schema with an owner column (e.g.
user_id). - Enable Row-Level Security and add policies so each authenticated user can only
select,insert,update,deletetheir own rows. Key the policy off the authenticated user id. - Provide typed queries/helpers that always run under the user's identity.
- Write and run a cross-user isolation test: as user A, attempt to read and write user B's rows — both must fail. Do not mark done until this test passes.
Adapting to other databases
The pattern is universal: an owner column + a policy/middleware that scopes every query to the authenticated principal + a test that proves cross-user access is denied. Swap the RLS syntax for your DB's equivalent (policies, query scoping, or an ORM guard).
Done when
The isolation test passes and the security-review skill returns PASS for this table.
Token tactics
Pass ONLY the table spec, not the repo. Reuse the cached instructions across tables. Route to a frontier model — a subtle isolation bug is a data breach.