rigorous-data-audit SKILL.md skillA
rigorous-data-audit from willy92wins/dayz-modding-knowledge-pack is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add willy92wins/dayz-modding-knowledge-pack/rigorous-data-audit@git:20261001.e42d2f4Pins git:20261001.e42d2f4 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- willy92wins/dayz-modding-knowledge-pack
- Path
skills/rigorous-data-audit/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261001.e42d2f4, committed Oct 1, 2026
- First version recorded
- Sep 1, 2026
- Size
- 48,801 bytes
- Repository stars
- 17
- License
- MIT
Use when: audit X, revisa a fondo, release-safe?, esto puede romper progresión, data loss, OnStoreSave/OnStoreLoad. Persistence/state-machine pre-release audit. Not cosmetic/UI: dayz-ui-development; not output-discipline: pre-output-discipline.
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
# Rigorous Data Audit Procedure for auditing mods where a bug equals lost player progression. Built from a real failure: six parallel Opus reasoning agents reviewed LF_VStorage 1.4.6 from independent angles and signed off as "release-safe" — an external implementer-grade audit then found 12 VULNs (P0–P3) the agents missed. This skill encodes the lessons. A second failure refined it further: a loose application of this skill's "parallel agents + consolidation" shape — pointed at fact-checking a corpus — produced an audit that was **~55% confabulated**, because there was no adversarial verification step between "agents reported it" and "acting on it". Step 3 below exists because of that. See `postmortem.md` for the case. Read `references/why-this-skill-exists.md` for the full retrospective if you want the original case study. ## When to invoke Trigger automatically when any of these are true: - Mod touches persistence, save files, state machines, or async work queues - A bug would cause **silent data loss** (lost items, wrong sids, money loss) - User asks for "audit", "revisa a fondo", "release-safe?", "puede romper progresión" …
Read the whole file at its exact version.
How to install
mdr add willy92wins/dayz-modding-knowledge-pack/rigorous-data-audit@sha256:dfdf8ec2eb0043e2The line at the top of this page pins the label git:20261001.e42d2f4, 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_2axlar3o66fjv6uj)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 1, 2026 and Oct 1, 2026, about one every 7 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261001.e42d2f4 latest | 2026-10-01 | e42d2f4 | 48,801 B | A | view · diff |
| git:20261001.74a473f | 2026-10-01 | 74a473f | 49,916 B | A | view · diff |
| git:20260924.fa4f23e | 2026-09-24 | fa4f23e | 49,058 B | A | view · diff |
| git:20260902.a5e8c87 | 2026-09-02 | a5e8c87 | 47,007 B | A | view · diff |
| git:20260901.b567e65 | 2026-09-01 | b567e65 | 46,552 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 (48801 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
willy92wins/dayz-modding-knowledge-pack · 17 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_2axlar3o66fjv6uj GET https://markdownregistry.com/api/v1/resolve?ref=willy92wins/dayz-modding-knowledge-pack/rigorous-data-audit GET https://markdownregistry.com/api/v1/blob/dfdf8ec2eb0043e2b28980de2ed7e68af206e506260eff8294ab6474b4ef75ee
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.