ai-agents-failure-archaeology SKILL.md skillA
ai-agents-failure-archaeology from rjmurillo/ai-agents is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add rjmurillo/ai-agents/ai-agents-failure-archaeology@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- rjmurillo/ai-agents
- Path
.claude/skills/ai-agents-failure-archaeology/SKILL.md- Versions recorded
- 5
- Latest version
- v1.0.0, committed Sep 25, 2026
- First version recorded
- Aug 1, 2026
- Size
- 16,964 bytes
- Repository stars
- 48
- License
- MIT
The chronicle of this repo's settled battles. Maps each major incident to symptom, root cause, evidence path, and the artifact that fixed it, so nobody re-fights a decided question. Use when you say `has this failed before`, `why does this rule exist`, `failure archaeology`, `what happened with issue 2205`. Do NOT use for triaging a live failure (use `ai-agents-debugging-playbook`) or for extracting learnings from the current session (use `retrospective`).
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
# ai-agents Failure Archaeology <!-- vendor-portability: contributor-facing knowledge pack for the rjmurillo/ai-agents repo itself; intentionally references upstream paths (.agents/, .claude/, scripts/, build/) because its audience is repo contributors, not plugin consumers (issue #2050) --> This repo's rules are fossils of incidents. Before you challenge a gate, weaken a guard, or propose a "simpler" approach, check whether that battle was already fought and what it cost. The canon lives in `.project-toolkit/retrospective/` and `.serena/memories/`; the provenance table below carries the commands that count both. Full local history is present (`git rev-list --count HEAD` = ~1471 as of 2026-07-03), but retro-cited short SHAs (e.g. `ddb76e0`, `01e76615a`) may not resolve locally, so archaeology still routes through the retros and memories as primary sources, not `git log`. Depth per incident lives in `references/incidents.md` (read it when a table row below is not enough). This file is the index and the verdict list. ## Triggers - `has this failed before` - `why does this rule exist` - `failure archaeology` - `what happened with issue 2205` …
Read the whole file at its exact version.
How to install
mdr add rjmurillo/ai-agents/ai-agents-failure-archaeology@sha256:496a9b51e4ab6784The line at the top of this page pins the label v1.0.0, 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_xdsivzjht3ho3utl)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Aug 1, 2026 and Sep 25, 2026, about one every 14 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-09-25 | 3fda96c | 16,964 B | A | view · diff |
| v1.0.0 | 2026-09-23 | efd148e | 16,755 B | A | view · diff |
| v1.0.0 | 2026-09-12 | fcc5ea0 | 16,656 B | A | view · diff |
| v1.0.0 | 2026-08-03 | f570d69 | 16,580 B | A | view · diff |
| v1.0.0 | 2026-08-01 | 9aa8e50 | 16,288 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 (16964 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
rjmurillo/ai-agents · 48 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_xdsivzjht3ho3utl GET https://markdownregistry.com/api/v1/resolve?ref=rjmurillo/ai-agents/ai-agents-failure-archaeology GET https://markdownregistry.com/api/v1/blob/496a9b51e4ab6784968daaa235b7c015e06ced69ab1f70a8082d078193a0a0f9
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.