Borrowing it
Nothing to install: this file belongs to charliehzm/medharness. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/charliehzm/medharness/main/.claude/skills/tdd-alignment/SKILL.mdgit clone --depth 1 https://github.com/charliehzm/medharnessWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/charliehzm/medharness/tdd-alignment)<a href="https://agentmods.dev/skills/charliehzm/medharness/tdd-alignment"><img src="https://agentmods.dev/badge/skills/charliehzm/medharness/tdd-alignment/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/charliehzm/medharness/tdd-alignment"><img src="https://agentmods.dev/badge/skills/charliehzm/medharness/tdd-alignment.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00190 | $0.00830 |
| Opus 5 | $0.00095 | $0.00415 |
| Sonnet 5 | $0.00038 | $0.00166 |
| Haiku 4.5 | $0.00019 | $0.00083 |
Grade A, and why
tdd-alignment scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TDD Alignment (Step 2)
Core mental model
The TDD is the bridge between what (PRD) and how-to-test (later steps). Misalignment here propagates downstream: an acceptance criterion with no test design becomes an acceptance criterion with no test, becomes a feature shipped without proof.
What it produces
TDD_ALIGNMENT.md with:
- Coverage table: each PRD acceptance criterion → TDD test strategy
- PHI handling table: each L3/L4 field → desensitization step in TDD
- Stage validation table: each PRD stage → TDD's stage-level test plan
- Gaps list (sorted by severity)
Active context bundle
Always load first
- This
SKILL.md - Final PRD
- Submitted TDD
COMPLIANCE_TAG.md(PHI field list)
Load on demand
reference/test-strategy-catalog.md(unit / integration / e2e / chaos / compliance / replay)
Workflow
- Extract PRD acceptance criteria into a flat list (numbered).
- For each criterion, find the TDD section that addresses it; record (criterion → tdd-section + test-strategy).
- Any criterion without a target → gap.
- For every L3/L4 field in COMPLIANCE_TAG, locate desensitization plan in TDD; missing → gap.
- For every PRD stage, locate the corresponding TDD stage validation; missing → gap.
- Emit report; if gaps exist, suggest concrete TDD patches.
Hard gate checklist
- 100% of PRD criteria covered (no gaps)
- Every L3/L4 field has desensitization step named in TDD
- Each PRD stage has corresponding TDD stage validation
- Test strategy named (not just "we'll test it")
Common failure modes
- "Tests will be written later" handwave: TDD says "comprehensive testing" without naming approach. Mitigation: require strategy name from
reference/test-strategy-catalog.md. - Forgotten staging tests: PRD has 3 stages, TDD only describes final-state tests. Mitigation: per-stage row in alignment table.
- PHI assumed handled by infra: developer assumes desensitize happens "somewhere". Mitigation: explicit row per field.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 11d ago First seen · 68 lines · 190 tokens per session scan A 5bafc76b0e77
tdd-alignment is a skill published in the GitHub repository charliehzm/medharness (86 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 190 tokens to every session and 830 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
HIPAA Compliance Testing
Testing HIPAA compliance for healthcare applications including PHI handling, audit logging, access controls, and data encryption verification.
writing-skills
A guide for creating and testing reusable instructions for AI agents, called skills. It applies test-driven development, or TDD—the practice of writing tests before implementation—to instruction documents.
test-driven-development
Test-driven development, or TDD, is a way to build software by writing a test that fails, adding the smallest code that makes it pass, and then cleaning up the code. These instructions require that process for features, bug fixes, refactors, and behavior changes.
test-driven-development
Use when the user explicitly requests strict or test-first TDD, or when the current conversation already contains an explicit TDD Route: strict decision from another Aegis workflow.
laravel-tdd
Test-driven development for Laravel with PHPUnit and Pest, factories, database testing, fakes, and coverage targets.
react-web
React web development with hooks, React Query, Zustand.