hex-persistence SKILL.md skillA
hex-persistence from wntic/pyhouse is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add wntic/pyhouse/hex-persistence@git:20261014.20fc6e0Pins git:20261014.20fc6e0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- wntic/pyhouse
- Path
plugins/pyhouse-hex/skills/hex-persistence/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261014.20fc6e0, committed Oct 14, 2026
- First version recorded
- Sep 30, 2026
- Size
- 12,954 bytes
- Repository stars
- 3
- License
- MIT
Use when one hexagonal service's own relational layer changes — the `Table` and its constraints, the repository adapter satisfying a domain repository protocol, the paired Alembic revision, or the store's settings class with its engine and repository binding — or when one command must write two or more repositories atomically through a unit of work. Owns the SQLAlchemy Core templates binding `persistence`'s store-generic rules — the shared naming convention, the entity mapper, the…
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
# Hexagonal Persistence (relational) The table, the repository that queries it, and the migration that ships it, kept together because the constraint names are one contract across all three (`persistence` rule 7). **Load `persistence` before writing any file below**; the templates satisfy its rules and do not restate them. The rules here are the hexagonal shape around them: an adapter behind a port, its two constructor forms, the paired revision and the unit of work. For a non-relational store — a key-value, cache or document backend — use the client-repository form instead. The store profile decides which applies (`hex-conventions` block B). ## When to use vs. neighbours - The obligations any store's data access meets, whatever the family — transaction ownership, driver-error translation, constraint names, row mapping, stored types and indexes, conflicts and ordering, safe schema changes → `persistence`; this skill binds them. - A persistent table, its columns, constraints or indexes → `TABLE.md`. - The adapter satisfying a domain repository protocol on a relational store → `REPOSITORY.md`. - The migration pairing with a schema change → `REVISION.md`. …
Read the whole file at its exact version.
How to install
mdr add wntic/pyhouse/hex-persistence@sha256:eb6c09912919bda0The line at the top of this page pins the label git:20261014.20fc6e0, 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.
[](https://markdownregistry.com/a/art_pj7wjg5up6o6t4kl)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 30, 2026 and Oct 14, 2026, about one every 3 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261014.20fc6e0 latest | 2026-10-14 | 20fc6e0 | 12,954 B | A | view · diff |
| git:20261011.7343419 | 2026-10-11 | 7343419 | 12,945 B | A | view · diff |
| git:20261001.5e36609 | 2026-10-01 | 5e36609 | 13,064 B | A | view · diff |
| git:20261001.7f0f354 | 2026-10-01 | 7f0f354 | 13,064 B | A | view · diff |
| git:20260930.b2b03ca | 2026-09-30 | b2b03ca | 12,422 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (12954 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
wntic/pyhouse · 3 stars · license MIT · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_pj7wjg5up6o6t4kl GET https://markdownregistry.com/api/v1/resolve?ref=wntic/pyhouse/hex-persistence GET https://markdownregistry.com/api/v1/blob/eb6c09912919bda0f8d0a281d9cfa77640ecb929c0cff053fe9ef6da2bdb1d4b
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.