model-release-intake skillA
model-release-intake is agent-read markdown (skill) from clickety-clacks/tightbeam: Ceremony for taking in a newly released (or retired) model — detect catalog drift, characterize the new mind, update the single activity table, and attest. Trigger is a human noticing a release, or `mix tightbeam.catalog.diff` reporting drift..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified before it reaches your agent: the main file against the SHA-256 recorded here, the others against the git hashes of its source commit. The deterministic audit below grades the latest version, and the same checks always give the same file the same grade.
What the file says
# Model release intake A new model shipped, or an old one vanished, and the catalog no longer matches the judgment the org has written down. This is a rare, deliberate ceremony — not automation. You run it when a human notices a release or when the drift detector flags it. The goal is that every model an agent can be handed is a model someone has characterized, and every characterization still names a model that exists. ## When to run - `mix tightbeam.catalog.diff` exits nonzero (uncharacterized live refs, or characterized refs that have vanished from the live inventory), OR - a human learns a model was released, renamed, retired, or repriced. ## Steps 1. **Detect.** Run the diff and read it as the worklist: ``` mix tightbeam.catalog.diff # human report; nonzero exit on drift mix tightbeam.catalog.diff --json # machine-readable, same exit contract ``` - UNCHARACTERIZED live refs → new minds to characterize (steps 2-4). - VANISHED characterized refs → retired minds to remove or re-point (step 5). 2. **Characterize each new model.** Add an entry to the working-set section of …
Read the whole file at its exact version.
How to install
mdr add clickety-clacks/tightbeam/model-release-intake@git:20260830.423449cmdr add clickety-clacks/tightbeam/model-release-intake@sha256:9a63ce7a33cf6467Pin to a label to follow the author's releases, or to a sha256 for exact bytes. Either way the resolved hash is written to mdr.lock, and mdr install fetches those bytes again and checks them, so it installs them exactly or fails.
[](https://markdownregistry.com/a/art_o65dx6m6p5umziws)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260830.423449c latest | 2026-08-30 | 423449c | 3,764 B | A | view · diff |
| git:20260830.cbb6d69 | 2026-08-30 | cbb6d69 | 3,729 B | A | view · diff |
| git:20260723.7608dd1 | 2026-07-23 | 7608dd1 | 3,914 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 (3764 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
clickety-clacks/tightbeam · 14 stars · license none · pushed 2026-09-27 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_o65dx6m6p5umziws GET https://markdownregistry.com/api/v1/resolve?ref=clickety-clacks/tightbeam/model-release-intake GET https://markdownregistry.com/api/v1/blob/9a63ce7a33cf6467602f829802fccf6fe7c7b822781068e777c62001f9765b78
Your agent 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.