live-gate SKILL.md skillA
live-gate from sshadows/lethal is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add sshadows/lethal/live-gate@git:20261023.f924fd4Pins git:20261023.f924fd4 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- sshadows/lethal
- Path
.claude/skills/live-gate/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261023.f924fd4, committed Oct 23, 2026
- First version recorded
- Oct 21, 2026
- Size
- 5,610 bytes
- Repository stars
- 10
- License
- MIT
Run the LethAL live integration gate against the Cronus BC container — the frozen per-mutant tables through both backends. Use when validating a layer end-to-end on live infra, or when the user says "run the live gate" / "run the itests live". Publishes to a live BC container, so it is user-invoked only.
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
# Live gate The authority for LethAL correctness (unit tests are structurally blind to AL that can't compile / real BC behavior). Runs the env-gated integration itests foreground and checks the frozen per-mutant tables. A differing verdict = BLOCKED (a real regression), never "close enough". ## Prerequisite: harness + publish order (bcdev path) The instrumented target depends on the `LethAL Control` extension and every RunMutant routes through it. Publish order to the server (one of the BC on Linux servers `bc1`-`bc3`, which `scripts/bc-linux-setup.ts` prepares; Cronus28 is parked, and Cronus284 is CentralGauge's, never LethAL's): 1. `LethAL Control` (`extensions/lethal-control`) — must expose `HarnessInfo`, `RegisterArtifact` is IN-PROCESS only (no OData write), `RegisteredArtifact` + `RunMutant` OData actions. 2. The instrumented sandbox target (the itest publishes it — needs the LethAL Control dependency + `lethal-control.app` symbol staged). 3. `fixtures/sandbox-tests`. 4. `fixtures/sandbox-probes` (protocol-invariant probes). Precondition: at most ONE instrumented target installed per container; no concurrent/external publish during the run. …
Read the whole file at its exact version.
How to install
mdr add sshadows/lethal/live-gate@sha256:6e663e5aae66b337The line at the top of this page pins the label git:20261023.f924fd4, 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_srxybtlwse2y7ijc)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Oct 21, 2026 and Oct 23, 2026, more than one a day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261023.f924fd4 latest | 2026-10-23 | f924fd4 | 5,610 B | A | view · diff |
| git:20261023.834214e | 2026-10-23 | 834214e | 5,406 B | A | view · diff |
| git:20261023.e31a209 | 2026-10-23 | e31a209 | 4,817 B | A | view · diff |
| git:20261021.98334d7 | 2026-10-21 | 98334d7 | 4,917 B | A | view · diff |
| git:20261021.69a7f00 | 2026-10-21 | 69a7f00 | 5,943 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 (5610 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
sshadows/lethal · 10 stars · license MIT · pushed 2026-11-07 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_srxybtlwse2y7ijc GET https://markdownregistry.com/api/v1/resolve?ref=sshadows/lethal/live-gate GET https://markdownregistry.com/api/v1/blob/6e663e5aae66b3379414e02e6554b9fe1b819ad1ab7a2e73c698ac763cd786c8
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.