Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add Aimeerrhythm/enterprise-change-workflow --skill tddgit clone --depth 1 https://github.com/Aimeerrhythm/enterprise-change-workflowWrote 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/aimeerrhythm/enterprise-change-workflow/tdd)<a href="https://agentmods.dev/skills/aimeerrhythm/enterprise-change-workflow/tdd"><img src="https://agentmods.dev/badge/skills/aimeerrhythm/enterprise-change-workflow/tdd.svg" alt="Measured on agentmods" 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.00027 | $0.01745 |
| Opus 5 | $0.00014 | $0.00873 |
| Sonnet 5 | $0.00005 | $0.00349 |
| Haiku 4.5 | $0.00003 | $0.00175 |
Grade A, and why
tdd 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 7d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test-Driven Development (TDD)
Overview
Write the test first. Watch it fail. Write minimal code to pass.
Core principle: If you didn't watch the test fail, you don't know if it tests the right thing.
Announce at start: "Using ecw:tdd to guide test-first implementation."
Scope Boundary
ecw:tdd executes the Red-Green(-Refactor) cycle. It does NOT own design decisions.
Requirement changes (Plan exists)
Before writing any test, read the Plan file (.claude/plans/<name>.md). All file paths, method signatures, test scenarios, error codes, and data formats are specified there.
What this skill MUST do:
- Read the Plan to get file paths, test scenarios, and expected behavior
- Write failing tests (RED) per Plan specification
- Write minimal implementation to pass tests (GREEN)
- Run compilation and tests to verify
What this skill MUST NOT do:
- Ask design questions via AskUserQuestion (data format, field naming, storage approach — these belong to writing-plans). If a design gap is found, note it in output and proceed with the Plan's specification.
- Rewrite or update the Plan file (if the Plan is wrong, finish current Task's TDD first, then report the discrepancy)
- Explore the codebase to rediscover what the Plan already specifies (file paths, class names, method signatures are in the Plan)
- Create new Tasks beyond what the Plan defines
Handling factual errors in the Plan (class not found, method signature mismatch, wrong file path):
- One verification Read is allowed to confirm the error is real (not a typo in your code)
- If confirmed, note the discrepancy in output, adapt minimally to make the test compile, and continue
- Do NOT use this as a loophole for general exploration — one targeted Read per error, not open-ended searching
Bug fixes (no Plan — input from systematic-debugging)
Bug fixes skip writing-plans. The input is the root cause analysis from ecw:systematic-debugging, not a Plan file.
What this skill MUST do:
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 146 lines · 27 tokens per session scan A 70243e416fd2
tdd is a skill published in the GitHub repository Aimeerrhythm/enterprise-change-workflow (1 stars, last pushed 3mo ago), licensed MIT. It adds 27 tokens to every session and 1,745 once invoked, about $0.0001 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-31.
Other skills, from other repositories
qa
QA testing — browse like a real user, document bugs, report only. Never fixes.
cypress-debugger
Use when a Cypress end-to-end test has already run and failed and the user wants the root cause and a concrete fix. Trigger on a failing Cypress spec, Timed-out-retrying command, unresolved selector, cy.intercept alias or request race, suite-breaking hook, retry-only flake, hydration or timing race, or a…
playwright-debugger
Use when a Playwright end-to-end test has already run and failed and the user wants the root cause and a concrete fix. Trigger on a failing Playwright spec, TimeoutError, broken or ambiguous selector, post-deploy suite failure, retry-only flake, hydration or timing race, or a passes-locally-but-fails-in-CI split.…
debug
Systematic bug investigation with a five-phase framework: reproduce, narrow, diagnose, fix, verify. Supports automated regression bisect via --regression flag. Produces a structured debug report with root cause analysis, regression test, and CQ/Q self-evaluations.
Vitest Mock Isolation Review
Detects Vitest test-isolation hazards: unrestored vi.spyOn/vi.mock without afterEach cleanup or restoreMocks config, un-awaited resolves/rejects assertions, and shared mutable module state across tests.
g-review
Run the review gate on the current branch diff. Runs the test suite, captures the diff, and dispatches code-lead, which verifies done conditions and reviews the diff itself. Issues MERGE READY or HOLD.