security-incident skillA
security-incident is agent-read markdown (skill) from clickety-clacks/tightbeam: Run a security incident lawfully — credential exposure, leaked secrets, compromised authority. Quarantine authority by convention while preserving evidence rows immutable, impose a notification moratorium with named exit conditions, and route admissibility to the owner with rotation-or-acceptance as the exits. Use the moment an exposure is observed or reported..
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
# Security incident — quarantine of authority The lawful form of a freeze is coordination, never mechanism: the substrate holds nothing, judges nothing, and seizes nothing, so a security incident is handled by agents agreeing — on the record — to stop honoring an authority while its owner rules. Separate the two things an incident touches and treat them oppositely: - **EVIDENCE is preserved immutable.** The rows that show the exposure — attests, wakes, transcripts — are never deleted, edited, or "cleaned up." File a specimen citing the observed row ids and naming the class. Losing evidence to tidiness is a second incident. - **AUTHORITY is suspended by convention.** The exposed credential, session, or role keeps its substrate powers — no substrate hold exists, by ruling — and the org simply stops honoring them: no new cards dispatched to it, its directives not propagated, its verdicts held un-relied-upon, pending the owner's ruling. Every agent told of the quarantine records that it is observing it. ## The credential-exposure protocol 1. **Never quote values.** Name WHERE the credential was exposed (file, row id, …
Read the whole file at its exact version.
How to install
mdr add clickety-clacks/tightbeam/security-incident@git:20260813.e697451mdr add clickety-clacks/tightbeam/security-incident@sha256:4f974602c7571fe4Pin 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_5tvuzoymv73ezp6v)
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 (3179 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_5tvuzoymv73ezp6v GET https://markdownregistry.com/api/v1/resolve?ref=clickety-clacks/tightbeam/security-incident GET https://markdownregistry.com/api/v1/blob/4f974602c7571fe4c0692ef4958d880f88013a285d481bc3dc999baedbf7daae
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.