lagune-verify SKILL.md skillA
lagune-verify from wellwelwel/lagune is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add wellwelwel/lagune/lagune-verify@git:20261104.6b619eePins git:20261104.6b619ee in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- wellwelwel/lagune
- Path
skills/lagune-verify/SKILL.md- Versions recorded
- 7
- Latest version
- git:20261104.6b619ee, committed Nov 4, 2026
- First version recorded
- Oct 31, 2026
- Size
- 14,376 bytes
- Repository stars
- 174
- License
- Apache-2.0
Prove each applied control holds by confronting the hardening record with the code, writing each verdict back into that record, then standing the findings proven closed out of the chain. Read-only on your code, it writes only Lagune's own chain.
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
## User Input <user-input> $ARGUMENTS </user-input> The User Input above decides how this command runs. Read it before proceeding. A placeholder left unfilled above is not the input: the User Input is then the words that came with this command, or empty when there are none. ## Outline You are proving that the controls hardening applied **actually hold**, and writing each verdict back into the **hardening record** at `.lagune/memory/harden.md`. This phase **produces no artifact of its own**: a verdict lives on its control's block, where harden reads it next run, and the session summary is your report to the user. It **continues from harden**, which already applied the controls, so it re-applies nothing: it proves what is there, for controls really in the record, never one you imagine. Think of this phase as a **detect focused on the fixes**. It reads each place the record says a control was applied and confirms the code matches. The proof is this confrontation of **the record's claim against what the code shows** (Step 4 names how they can disagree), never a test you write or the system run live. …
Read the whole file at its exact version.
How to install
mdr add wellwelwel/lagune/lagune-verify@sha256:7b4c0de3e17b0f9cThe line at the top of this page pins the label git:20261104.6b619ee, 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_3nvqui6kq7iprmbg)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 7 versions of this file, between Oct 31, 2026 and Nov 4, 2026, more than one a day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261104.6b619ee latest | 2026-11-04 | 6b619ee | 14,376 B | A | view · diff |
| git:20261103.aa41128 | 2026-11-03 | aa41128 | 14,376 B | A | view · diff |
| git:20261102.0ad572c | 2026-11-02 | 0ad572c | 14,376 B | A | view · diff |
| git:20261102.262f3a9 | 2026-11-02 | 262f3a9 | 14,304 B | A | view · diff |
| git:20261031.31d7d11 | 2026-10-31 | 31d7d11 | 14,418 B | A | view · diff |
| git:20261031.35c92c8 | 2026-10-31 | 35c92c8 | 14,271 B | A | view · diff |
| git:20261031.955e4ae | 2026-10-31 | 955e4ae | 14,053 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 (14376 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
wellwelwel/lagune · 174 stars · license Apache-2.0 · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_3nvqui6kq7iprmbg GET https://markdownregistry.com/api/v1/resolve?ref=wellwelwel/lagune/lagune-verify GET https://markdownregistry.com/api/v1/blob/7b4c0de3e17b0f9c326880b983684790f6d0d21f331d7b113645811490573b97
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.