Home / cogvera-labs / next-expo-supabase-agent-harness · GitHub

AGENTS.md@template/stack/supabaseA

AGENTS.md@template/stack/supabase from cogvera-labs/next-expo-supabase-agent-harness is an AGENTS.md file: the standing instructions coding agents read in that repo.

Install it, pinned

mdr add cogvera-labs/next-expo-supabase-agent-harness/template/stack/supabase/AGENTS.md@git:20261021.a22139a

Pins git:20261021.a22139a in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 14 of 14 checks passed
Kind: AGENTS.md file
Repository: cogvera-labs/next-expo-supabase-agent-harness
Path: template/stack/supabase/AGENTS.md
Versions recorded: 4
Latest version: git:20261021.a22139a, committed Oct 21, 2026
First version recorded: Jul 25, 2026
Size: 3,748 bytes
Repository stars: 8
License: Apache-2.0

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# supabase — the shared backend (schema, RLS, tests, functions)

ONE Postgres database that the Next web host and the Expo mobile client both reach through the
SAME RLS policies. Schema truth is SQL-first; there is no ORM.

## Layout

- `schemas/*.sql` — the DECLARATIVE source of truth (`00_shared`, `10_account`, `20_notes`, …),
  the desired end-state a reviewer reads.
- `migrations/<timestamp>_<slice>.sql` — the APPLIED, append-only history. `supabase db push`
  records a migration by FILENAME, so editing an already-applied file changes nothing on a
  database that ran it and silently diverges deployed schema from committed history. Never edit
  or delete a committed migration — add a new timestamped one (`supabase migration new`).
- `tests/*.sql` — pgTAP. `rls_structure.test.sql` reads back what the database compiled;
  `rls_isolation.test.sql` proves the empty-set principle through raw role-switch. Both run on
  `pnpm db:test` and are the structural twin of `tests/rls/` (the supabase-js client suite).
  `rls_grants.generated.test.sql` is GENERATED by `node tools/gen-grant-assertions.mjs`.
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add cogvera-labs/next-expo-supabase-agent-harness/template/stack/supabase/AGENTS.md@sha256:f9f949920194d7e2

The line at the top of this page pins the label git:20261021.a22139a, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

[![mdr](https://markdownregistry.com/badge/art_nbijn6rbkuadhsvn.svg)](https://markdownregistry.com/a/art_nbijn6rbkuadhsvn)

1 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 4 versions of this file, between Jul 25, 2026 and Oct 21, 2026, about one every 30 days.

version	committed	commit	size	audit
git:20261021.a22139a latest	2026-10-21	a22139a	3,748 B	A	view · diff
git:20260930.1462bf9	2026-09-30	1462bf9	3,544 B	A	view · diff
git:20260920.8d588cb	2026-09-20	8d588cb	3,340 B	A	view · diff
git:20260725.ec9abcb	2026-07-25	ec9abcb	2,961 B	A	view

Audit of the latest version

A 14 of 14 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Size between 200 bytes and 200 KB (3748 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag

Source

GitHub

cogvera-labs/next-expo-supabase-agent-harness · 8 stars · license Apache-2.0 · pushed 2026-11-07 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_nbijn6rbkuadhsvn
GET https://markdownregistry.com/api/v1/resolve?ref=cogvera-labs/next-expo-supabase-agent-harness/template/stack/supabase/AGENTS.md
GET https://markdownregistry.com/api/v1/blob/f9f949920194d7e2fcaf3d816d94edc29d5afcac2d9df6a0296d025f269feaa3

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: how to write a good AGENTS.md · AGENTS.md vs CLAUDE.md · which agent file does what.

More from cogvera-labs/next-expo-supabase-agent-harness

authoring-e2ee-feature SKILL.md skill

cogvera-labs/next-expo-supabase-agent-harness · plugin/skills/authoring-e2ee-feature/SKILL.md · The decide-the-columns -> schema -> ciphertext DAL -> seal/open at the screen -> store-policy -> DSR record ->…