session-boundary SKILL.md skillA
session-boundary from restarter/lets-workflow is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add restarter/lets-workflow/session-boundary@git:20260926.8edfea9Pins git:20260926.8edfea9 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- restarter/lets-workflow
- Path
plugins/lets/skills/session-boundary/SKILL.md- Versions recorded
- 4
- Latest version
- git:20260926.8edfea9, committed Sep 26, 2026
- First version recorded
- Sep 4, 2026
- Size
- 9,022 bytes
- Repository stars
- 17
- License
- MIT
Internal skill for commands. Resolve and VALIDATE this branch's session boundary - the ref a session's commit range is measured from - and report how much it can be trusted. Do not trigger on user conversation; only when a command needs the session range.
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
# Session Boundary Resolve the ref a session's commit range is measured from, validate it, and say how far it can be trusted. `/lets:end` needs it EARLY (it gates which settlements are offered) and `session-snapshot` needs it LATE (the `### Range` block it writes into a durable file). Two copies of a validation ladder drift, and drift here is what produced a confident "260 commits" for a 6-commit session (lets-370mx), so the ladder lives here and nowhere else. **Contract:** no args. Output: four echoed lines the caller reads VERBATIM. ``` SESSION_BOUNDARY=<sha | none> SESSION_TRUST=<exact | prior-session | estimate | none> SESSION_COMMITS=<N | unknown> SESSION_RANGE_DESC=<one-line human description, always carrying the trust level> ``` Diagnostic NOTEs go to stderr - surface them to the user, they are the loud half of every degradation. **Fail closed.** If the four lines do not arrive, the caller MUST assume `SESSION_TRUST=none` / `SESSION_COMMITS=unknown` and proceed as though no boundary exists. Never re-derive one inline - a second copy is a second answer, which is the defect this skill exists to prevent. ## Trust levels | level | boundary | what the caller may claim | …
Read the whole file at its exact version.
How to install
mdr add restarter/lets-workflow/session-boundary@sha256:ca217d72a061ea81The line at the top of this page pins the label git:20260926.8edfea9, 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_euvusayd67op6qrf)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Sep 4, 2026 and Sep 26, 2026, about one every 7 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260926.8edfea9 latest | 2026-09-26 | 8edfea9 | 9,022 B | A | view · diff |
| git:20260926.e1f4c0d | 2026-09-26 | e1f4c0d | 8,902 B | A | view · diff |
| git:20260904.a5b67d1 | 2026-09-04 | a5b67d1 | 8,842 B | A | view · diff |
| git:20260904.c539f4b | 2026-09-04 | c539f4b | 7,035 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 (9022 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
restarter/lets-workflow · 17 stars · license MIT · pushed 2026-11-03 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_euvusayd67op6qrf GET https://markdownregistry.com/api/v1/resolve?ref=restarter/lets-workflow/session-boundary GET https://markdownregistry.com/api/v1/blob/ca217d72a061ea81ac73adaaec3c9c575556168efa58ca3fab4d2cbdaa9fec4e
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.