verify-unattended SKILL.md skillA
verify-unattended from reticlehq/reticle is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add reticlehq/reticle/verify-unattended@v3.9.0Pins v3.9.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- reticlehq/reticle
- Path
skills/verify-unattended/SKILL.md- Versions recorded
- 18
- Latest version
- v3.9.0, committed Oct 29, 2026
- First version recorded
- Aug 21, 2026
- Size
- 8,159 bytes
- Repository stars
- 1,249
- License
- a license file GitHub does not identify
Install, instrument and verify a web app end to end without pausing for a human. Use in an autonomous or goal-mode agent, in CI, or in any client that asks for approval on every command: it never says "restart your client" or "open a browser", because it takes a route that needs neither. Prefer the normal reticle skill when a human is present and can answer.
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
# Reticle, unattended Same product, same verdicts, one difference: **nothing here waits for a human.** The normal skill has two places where it hands control back: "restart your client so it picks up the MCP server" and "open the app in a browser". Both are correct when someone is sitting there. In goal mode they are dead ends: the restart ends the context holding these instructions, and there is nobody to open a tab. So this skill takes the route that needs neither, and stops only when it has a verdict or a reason. ## The one rule that makes this work **You cannot add MCP tools to your own running process.** No slash command, no config edit, no re-registration reaches the tool list you already have. Your client read it before Reticle existed. Do not try, and do not ask to be restarted. Instead, branch once on what you already have: - **`reticle_*` tools present** → drive with them. Best evidence, source-mapped, full verdicts. - **not present** → use the CLI. `reticle verify` produces a verdict and an exit code with no MCP involvement at all. Both routes end in a verdict. Pick the one your process allows and go. ## Step 1: wire it, once …
Read the whole file at its exact version.
How to install
mdr add reticlehq/reticle/verify-unattended@sha256:a14c779aebf1e52aThe line at the top of this page pins the label v3.9.0, 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_j6j2llivsgqmahqq)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 18 versions of this file, between Aug 21, 2026 and Oct 29, 2026, about one every 4 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v3.9.0 latest | 2026-10-29 | f2e07e0 | 8,159 B | A | view · diff |
| v3.8.2 | 2026-10-26 | f8a40d5 | 8,159 B | A | view · diff |
| v3.8.1 | 2026-10-26 | a6b11ca | 8,159 B | A | view · diff |
| v3.8.0 | 2026-10-25 | 68dd8a1 | 8,159 B | A | view · diff |
| v3.7.0 | 2026-10-09 | 4019204 | 7,712 B | A | view · diff |
| v3.6.0 | 2026-10-07 | c08be48 | 7,712 B | A | view · diff |
| v3.5.0 | 2026-10-01 | 14085e6 | 7,712 B | A | view · diff |
| v3.4.0 | 2026-09-30 | 2685d9a | 7,712 B | A | view · diff |
| v3.3.0 | 2026-09-26 | 9af7d09 | 7,712 B | A | view · diff |
| v3.3.0 | 2026-09-25 | 0b8afcc | 7,611 B | A | view · diff |
| v3.2.0 | 2026-09-23 | d400c5d | 7,611 B | A | view · diff |
| v3.1.0 | 2026-09-18 | 5d475e0 | 7,611 B | A | view · diff |
| v2.14.0 | 2026-09-09 | f3be3a9 | 7,612 B | A | view · diff |
| v2.13.1 | 2026-09-02 | 96d872c | 7,612 B | A | view · diff |
| v2.13.0 | 2026-09-02 | a6ee238 | 7,612 B | A | view · diff |
| v2.12.0 | 2026-09-02 | 9814709 | 7,612 B | A | view · diff |
| v2.9.0 | 2026-08-27 | 33ad411 | 7,210 B | A | view · diff |
| v2.9.0 | 2026-08-21 | e019802 | 7,208 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 (8159 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
reticlehq/reticle · 1,249 stars · license a license file GitHub does not identify · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_j6j2llivsgqmahqq GET https://markdownregistry.com/api/v1/resolve?ref=reticlehq/reticle/verify-unattended GET https://markdownregistry.com/api/v1/blob/a14c779aebf1e52a2fd9c768195b6fcf708f0c67a671e48ce8ed06f76736152c
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.