recurrence-prevention SKILL.md skillA
recurrence-prevention from uzysjung/uzys-agent-harness is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add uzysjung/uzys-agent-harness/recurrence-prevention@git:20260920.d109313Pins git:20260920.d109313 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- uzysjung/uzys-agent-harness
- Path
.claude/skills/recurrence-prevention/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260920.d109313, committed Sep 20, 2026
- First version recorded
- Aug 2, 2026
- Size
- 21,900 bytes
- Repository stars
- 3
- License
- MIT
When the same defect, mistake, or incident happens AGAIN — a recurrence, not a one-off — verify it against prior evidence (memory, rule 근거 links, git/CHANGELOG history), classify it as a simple slip vs a complex harness problem, then re-evaluate the countermeasure that failed: repair or replace it, choosing a record, a one-line criterion, a code fix, or a structural gate (test, hook, derive) by evidence — more deterministic when prose has demonstrably failed, nothing new when repair suffices.…
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
# Recurrence Prevention (재발방지) A defect that happens once is a bug. A defect that happens **twice is a countermeasure failure** — whatever was supposed to prevent the second occurrence (a mental note, a memory entry, a rule) demonstrably did not. So on a recurrence, the unit of work is not the fix (you already know the fix — you applied it last time). The unit of work is the **countermeasure**: re-evaluate the cause analysis and whatever was supposed to prevent this, repair or replace it, and reach for a more deterministic mechanism only when repairing the existing one cannot suffice. **A recurrence is evidence for that re-evaluation, not an order to add a level.** This skill codifies a practice proven in the harness repo that ships it: the no-false-ship rule was created only after the *third* false-ship incident; CHANGELOG drift survived a written convention for seven releases and stopped only when a test gate enforced it; comment warnings against hardcoded-list drift failed twice before "derive to a single source" became mandatory. The pattern is consistent: **each enforcement level fails in a characteristic way, and when one …
Read the whole file at its exact version.
How to install
mdr add uzysjung/uzys-agent-harness/recurrence-prevention@sha256:c7c163aceb457535The line at the top of this page pins the label git:20260920.d109313, 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_jdgrnqipkcc6c6jy)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Aug 2, 2026 and Sep 20, 2026, about one every 12 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260920.d109313 latest | 2026-09-20 | d109313 | 21,900 B | A | view · diff |
| git:20260920.2c17d35 | 2026-09-20 | 2c17d35 | 21,125 B | A | view · diff |
| git:20260920.4f13f6d | 2026-09-20 | 4f13f6d | 19,252 B | A | view · diff |
| git:20260913.2b1286f | 2026-09-13 | 2b1286f | 19,254 B | A | view · diff |
| git:20260802.f93c659 | 2026-08-02 | f93c659 | 18,781 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 (21900 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
uzysjung/uzys-agent-harness · 3 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_jdgrnqipkcc6c6jy GET https://markdownregistry.com/api/v1/resolve?ref=uzysjung/uzys-agent-harness/recurrence-prevention GET https://markdownregistry.com/api/v1/blob/c7c163aceb457535adb3c3052fe41355048716db2cbb0b4cc768ca6fd4533f26
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.
More from uzysjung/uzys-agent-harness
Every file in uzysjung/uzys-agent-harness