tdd SKILL.md skillA
tdd from epicsagas/epic-harness is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add epicsagas/epic-harness/tdd@git:20260625.1c5e807Pins git:20260625.1c5e807 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- epicsagas/epic-harness
- Path
skills/tdd/SKILL.md- Versions recorded
- 4
- Latest version
- git:20260625.1c5e807, committed Jun 25, 2026
- First version recorded
- May 5, 2026
- Size
- 3,828 bytes
- Repository stars
- 20
- License
- Apache-2.0
Test-Driven Development enforcer. Red→Green→Refactor cycle with no production code without a failing test first. Use for new features and bug fixes.
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
# TDD — Test-Driven Development
## Iron Law
NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST. Violating the letter of this process is violating the spirit of this process.
## Process
### Red → Green → Refactor
1. **Red**: Write a failing test that describes the desired behavior
- Test name should read like a spec: `it("returns 401 when token is expired")` (reason: the test name IS your specification — it must communicate intent to future readers)
- Run the test — confirm it fails for the right reason (reason: a test that fails for the wrong reason gives false confidence)
2. **Green**: Write the minimum code to make the test pass
- Do not write more than needed — because premature optimization is the root of all evil; make it work first
- Do not optimize yet — because optimization without a passing test is speculation, not engineering
- Run the test — confirm it passes (reason: a passing test is the only proof the code works)
3. **Refactor**: Clean up without changing behavior
- Extract duplicates, rename for clarity, simplify — because readability matters more than cleverness
…Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_fwlu6jgjwurz4bnp/d67e81436b05d681fb17b87bd0bf9dcffbe3b16821b1ea1ca8adb55bfdbea0e1.json
Then /plugin install tdd@markdownregistry-fwlu6jgjwurz4bnp in Claude Code. It installs git:20260625.1c5e807, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add epicsagas/epic-harness/tdd@sha256:d67e81436b05d681The line at the top of this page pins the label git:20260625.1c5e807, 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_fwlu6jgjwurz4bnp)
0 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in epicsagas/epic-harness/tdd since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of tdd from somewhere else? Ask it: where did my tdd come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 4 versions of this file, between May 5, 2026 and Jun 25, 2026, about one every 17 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260625.1c5e807 latest | 2026-06-25 | 1c5e807 | 3,828 B | A | view · diff |
| git:20260506.2d8b529 | 2026-05-06 | 2d8b529 | 3,937 B | A | view · diff |
| git:20260505.9b60a97 | 2026-05-05 | 9b60a97 | 3,769 B | A | view · diff |
| git:20260505.8ddeaf8 | 2026-05-05 | 8ddeaf8 | 3,263 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/tdd/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
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 (3828 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
epicsagas/epic-harness · 20 stars · license Apache-2.0 · pushed 2026-11-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_fwlu6jgjwurz4bnp GET https://markdownregistry.com/api/v1/resolve?ref=epicsagas/epic-harness/tdd GET https://markdownregistry.com/api/v1/blob/d67e81436b05d681fb17b87bd0bf9dcffbe3b16821b1ea1ca8adb55bfdbea0e1
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 epicsagas/epic-harness
Every file in epicsagas/epic-harness