recon-lifecycle skillA
recon-lifecycle is agent-read markdown (skill) from clickety-clacks/tightbeam: A recon session answers one decidable question at decision grade, in one of four forms with its confidence, records it, closes its obligation, and ends. Use to scope, answer, and close an investigation..
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
# Recon lifecycle
A recon session exists to answer one question at decision grade, record the answer, and
end.
1. Fix the question at intake. Restate the question you were assigned as a decision the
answer will enable, and confirm the restatement against the assignment's subject.
Ask the "so what" test: if a finding would not change what the requester does, it is
out of scope. A question a finite body of evidence cannot settle will not
terminate — reshape it until it can, or return it to the requester. A recon without
a decidable question is returned for one.
2. Investigate to the standard of the answer, not exhaustively. The investigation ends
when the answer is proven, not when the territory is fully mapped. Findings beyond
the question are recorded as progress attests, not pursued.
3. Answer in exactly one of four forms:
- **yes** — proven, with the evidence that proves it;
- **no** — proven, with the evidence that proves it;
- **conditional** — yes under stated conditions, each condition named and checkable;
- **not-proven** — the evidence available cannot decide it; name the missing
evidence and the action that would produce it.
…Read the whole file at its exact version.
How to install
mdr add clickety-clacks/tightbeam/recon-lifecycle@git:20260723.7608dd1mdr add clickety-clacks/tightbeam/recon-lifecycle@sha256:d249de0d76b01390Pin 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_tnx5trhle4zszvht)
1 badge views in 30 days
Versions
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 (3401 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_tnx5trhle4zszvht GET https://markdownregistry.com/api/v1/resolve?ref=clickety-clacks/tightbeam/recon-lifecycle GET https://markdownregistry.com/api/v1/blob/d249de0d76b01390f4c390e390e579e329aca0950f39b81d59be8b7045eed317
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.