disputes-and-legal-holds skillA
disputes-and-legal-holds is agent-read markdown (skill) from cbrock84/headcount: Handles a dispute from the first sign of it — recognizing when preservation obligations attach, issuing and scoping a legal hold, suspending automatic deletion across every system that holds relevant material, preserving privilege, managing outside counsel and cost, and evaluating settlement against the real cost of continuing. Use this to respond to a claim or demand letter, issue a hold, work out which systems the hold has to reach, or decide whether to fight..
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 against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Disputes and legal holds The decisions that determine how a dispute goes are made in the first week, usually by people who do not know a dispute has started. **This structures the operational response. Procedural obligations and their deadlines vary by jurisdiction and forum — get counsel engaged early, and let them drive strategy.** ## Preservation attaches earlier than most people expect The obligation to preserve begins when litigation is reasonably anticipated — which can be a demand letter, a threat made in a meeting, a regulator's inquiry, or an internal complaint serious enough that a claim is foreseeable. It does not wait for a filing. **Destruction after that point is treated far more seriously than the underlying dispute.** Routine automatic deletion continuing through a hold is the common version, and "it was our normal policy" is not the defense people assume. ## Issue the hold in writing, and make it reach the systems A hold has two halves and organizations routinely do only the first. - **Notify the people.** Written, naming the matter in general terms, describing the categories of …
Read the whole file at its exact version.
How to install
mdr add cbrock84/headcount/disputes-and-legal-holds@git:20260916.e72e404mdr add cbrock84/headcount/disputes-and-legal-holds@sha256:44341396c9337121Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_fqx4oiuo6bo5ikqe)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260916.e72e404 latest | 2026-09-16 | e72e404 | 4,556 B | A | view · diff |
| git:20260901.d41b3ae | 2026-09-01 | d41b3ae | 4,217 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 (4556 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
cbrock84/headcount · 1,664 stars · license MIT · pushed 2026-09-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_fqx4oiuo6bo5ikqe GET https://markdownregistry.com/api/v1/resolve?ref=cbrock84/headcount/disputes-and-legal-holds GET https://markdownregistry.com/api/v1/blob/44341396c9337121081d0f792e37d32cf1c5843eab1beabda5275f25c7e89ff1
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.