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

authoring-e2ee-feature SKILL.md skillA

authoring-e2ee-feature from cogvera-labs/next-expo-supabase-agent-harness is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add cogvera-labs/next-expo-supabase-agent-harness/authoring-e2ee-feature@git:20261102.d0f625e

Pins git:20261102.d0f625e in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: cogvera-labs/next-expo-supabase-agent-harness
Path: template/base/.claude/skills/authoring-e2ee-feature/SKILL.md
Versions recorded: 5
Latest version: git:20261102.d0f625e, committed Nov 2, 2026
First version recorded: Sep 29, 2026
Size: 23,029 bytes
Repository stars: 8
License: Apache-2.0

The decide-the-columns -> schema -> ciphertext DAL -> seal/open at the screen -> store-policy -> DSR record -> reviewers recipe for encrypting one feature end-to-end with the opt-in e2ee module, so the server never holds plaintext or a key that decrypts it. Use when asked to encrypt a feature, add client-side encryption, or make a column unreadable to the server.

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

# Authoring an E2EE feature

Encryption sits ON TOP of the authorization boundary, never in place of it: RLS keyed on
`auth.uid()` still decides which rows a caller may read, and `@app/crypto` decides whether
the bytes mean anything once read. Everything in the `authoring-vertical-slice` recipe still
applies — migration, RLS, `./client` read, procedure, both screens, tests, provenance, green
gate. This recipe is what that slice gains when a column must be unreadable to the server,
and what it LOSES in exchange.

Build in this strict order. Steps 1, 5, 6 and 7 are irreversible-ish in different ways: a
column encrypted for a month cannot be retroactively indexed, and a user who loses the device
AND the recovery code cannot be given their data back.

## Step 0 — preconditions, all four

Do not start until all of these are true:

1. **You have read the full encryption rule, `.claude/rules/e2ee.md`.** It is path-scoped:
   it loads on its own only once a file under `packages/platform/crypto/`, a host seam under
   `apps/*/src/host/` or `docs/modules/e2ee/` has been read, and this recipe also edits
…

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/authoring-e2ee-feature@sha256:02012125d4ad291e

The line at the top of this page pins the label git:20261102.d0f625e, 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_p5avnx63jgipdacc.svg)](https://markdownregistry.com/a/art_p5avnx63jgipdacc)

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

Versions

The registry has recorded 5 versions of this file, between Sep 29, 2026 and Nov 2, 2026, about one every 9 days.

version	committed	commit	size	audit
git:20261102.d0f625e latest	2026-11-02	d0f625e	23,029 B	A	view · diff
git:20260930.1462bf9	2026-09-30	1462bf9	22,828 B	A	view · diff
git:20260930.a759379	2026-09-30	a759379	22,724 B	A	view · diff
git:20260930.8a4aa85	2026-09-30	8a4aa85	22,727 B	A	view · diff
git:20260929.fa385b0	2026-09-29	fa385b0	22,098 B	A	view

Audit of the latest version

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

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (23029 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_p5avnx63jgipdacc
GET https://markdownregistry.com/api/v1/resolve?ref=cogvera-labs/next-expo-supabase-agent-harness/authoring-e2ee-feature
GET https://markdownregistry.com/api/v1/blob/02012125d4ad291ead9572202e681a4a0d934786250a03d7352afdb8d77bcb2f

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: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · 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 ->…