tightbeam-assimilate skillA
tightbeam-assimilate is agent-read markdown (skill) from clickety-clacks/tightbeam: Onboard a machine as a tightbeam host — the complete assimilation ceremony (probe, credentials, archetype WHERE, restart, verify). Use when the operator asks to assimilate a machine..
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
Assimilation onboards a machine as a host. It is a CEREMONY you can run end-to-end when the operator asks — no source-diving, no guessing; this section is the complete procedure. 1. `tightbeam assimilate <ssh-dest> --as-user <operatorId>` (admin act — run it AS the operator who asked). <ssh-dest> is anything ssh resolves (tailnet names work). Preconditions the probe checks for you: key-based ssh access, node, npm and rsync on the target, and the CLI of every harness being enabled (`claude`, `codex`) — those are the operator's to install, never assimilation's, and the probe sees only what a non-interactive ssh session sees. Useful flags: --name <hostname> (defaults from the destination), --harness claude,codex, --dry-run (runs the probe for real and writes nothing, so it can and does fail). 1b. Cross-architecture satellites. The ceremony installs the CLI by shipping its own running binary, gated on identical target triples: a satellite whose OS/CPU differs from the control node SKIPS the CLI step with a warning (wi_c729ca10 tracks the product fix; the warning's "build for <target> and re-run" hint does not work from the control …
Read the whole file at its exact version.
How to install
mdr add clickety-clacks/tightbeam/tightbeam-assimilate@git:20260728.4dd0d39mdr add clickety-clacks/tightbeam/tightbeam-assimilate@sha256:a426044c43153b03Pin 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_dx6k3g3d4ws5nrhf)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260728.4dd0d39 latest | 2026-07-28 | 4dd0d39 | 3,353 B | A | view · diff |
| git:20260722.1f8d0e0 | 2026-07-22 | 1f8d0e0 | 3,068 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 (3353 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_dx6k3g3d4ws5nrhf GET https://markdownregistry.com/api/v1/resolve?ref=clickety-clacks/tightbeam/tightbeam-assimilate GET https://markdownregistry.com/api/v1/blob/a426044c43153b03fcfab2a8402eeadda7e515b9ce9d2a172b7b090b7b5b6799
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.