spike-consumer-adversarial SKILL.md skillA
spike-consumer-adversarial from testdouble/han is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add testdouble/han/spike-consumer-adversarial@git:20260709.3f87cf9Pins git:20260709.3f87cf9 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- testdouble/han
- Path
docs/plans/han-communication-plugin/artifacts/oi-3-spike/harness-skills/spike-consumer-adversarial/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260709.3f87cf9, committed Jul 9, 2026
- Size
- 1,745 bytes
- Repository stars
- 334
- License
- MIT
OI-3 spike harness — heavy consumer, ADVERSARIAL arm. Worst-case early-exit test: the mid-workflow Skill call has no continuation guardrail and the guidance skill ends with a final-sounding anchor. Use only when explicitly invoked by the spike harness with a TRIAL_ID and data path.
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
# Incident Post-Mortem Builder You are producing a written incident post-mortem report. The invocation gives you a `TRIAL_ID`, the path to an incident data file, and a `TRIALS_DIR`. ## Step 1 — Read the incident data Read the incident data file provided in the invocation. ## Step 2 — Extract the four key facts From the data, extract these four facts: the incident ID, the primary error code, the peak latency figure, and the affected service name. ## Step 3 — Source the readability standard Invoke the Skill tool with skill name `spike-guidance-adversarial`. ## Step 4 — Draft the report Write the incident post-mortem with these five labeled sections, applying the readability standard: 1. **Summary** — names the incident ID and the affected service. 2. **Impact** — states the peak latency figure. 3. **Root cause** — names the primary error code. 4. **Resolution** — how it was mitigated. 5. **Follow-up actions** — at least two. ## Step 5 — Self-check Check the draft against the standard. ## Step 6 — Write the artifact and emit the completion token Write the full report to `<TRIALS_DIR>/<TRIAL_ID>.md`. As the final line of that file, on its own line, write exactly: …
Read the whole file at its exact version.
How to install
mdr add testdouble/han/spike-consumer-adversarial@sha256:705713bc8415892aThe line at the top of this page pins the label git:20260709.3f87cf9, 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_kr327p7la6okrxur)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jul 9, 2026.
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 (1745 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
testdouble/han · 334 stars · license MIT · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_kr327p7la6okrxur GET https://markdownregistry.com/api/v1/resolve?ref=testdouble/han/spike-consumer-adversarial GET https://markdownregistry.com/api/v1/blob/705713bc8415892aa7aedc03d4d517edb04b2a164f236c5ba65cd5b78d555d42
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.