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 mnthe/hardworker-marketplace --skill tdd-workflowgit clone --depth 1 https://github.com/mnthe/hardworker-marketplaceWrote 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/mnthe/hardworker-marketplace/tdd-workflow)<a href="https://agentmods.dev/skills/mnthe/hardworker-marketplace/tdd-workflow"><img src="https://agentmods.dev/badge/skills/mnthe/hardworker-marketplace/tdd-workflow/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/mnthe/hardworker-marketplace/tdd-workflow"><img src="https://agentmods.dev/badge/skills/mnthe/hardworker-marketplace/tdd-workflow.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.00053 | $0.01691 |
| Opus 5 | $0.00026 | $0.00846 |
| Sonnet 5 | $0.00011 | $0.00338 |
| Haiku 4.5 | $0.00005 | $0.00169 |
Grade A, and why
tdd-workflow 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 9d 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 — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TDD Workflow
Test-Driven Development (TDD) workflow for tasks marked with approach: "tdd".
CRITICAL: TDD tasks MUST follow this exact sequence. Gate hooks will block out-of-order operations.
Scoped vs Full Test Execution
During TDD phases (RED/GREEN/REFACTOR):
- Run scoped tests only (specific test file or pattern)
- Fast feedback loop for the feature being developed
- Full test suite is deferred to VERIFY task
During VERIFICATION phase:
- Verifier runs full test suite (
npm testwithout scope) - Ensures no regressions across entire codebase
- PASS/FAIL determination based on complete test coverage
Why scoped execution?
- Speed: Test only what changed, not entire suite
- Focus: TDD cycle targets specific behavior
- Separation: Task implementation vs system verification
Using test_scope from Task
When task has test_scope field, use it for scoped execution:
# Read test_scope from task
TEST_SCOPE=$(bun "{SCRIPTS_PATH}/task-get.js" --session ${CLAUDE_SESSION_ID} --id {TASK_ID} --field test_scope)
# Run scoped test
npm test -- {test_scope}
Example task.json:
{
"id": "3",
"subject": "Add input validation",
"approach": "tdd",
"test_scope": "tests/validation.test.ts"
}
If test_scope is not set, use the test file path you created.
TDD Phase 1: RED - Write Failing Test
- Create test file FIRST (before any implementation code)
- Write test for expected behavior
- Run test and VERIFY IT FAILS
# Record test creation
bun "{SCRIPTS_PATH}/task-update.js" --session ${CLAUDE_SESSION_ID} --id {TASK_ID} \
--add-evidence "TDD-RED: Created test file tests/validateUser.test.ts"
# Run SCOPED test - MUST FAIL
npm test -- tests/validateUser.test.ts
# Record failure (expected)
bun "{SCRIPTS_PATH}/task-update.js" --session ${CLAUDE_SESSION_ID} --id {TASK_ID} \
--add-evidence "TDD-RED: npm test -- tests/validateUser.test.ts (exit code 1)"
Evidence Required:
- Test file path created
- Scoped test execution output showing failure
- Exit code 1 (expected)
- Evidence includes full test command with scope
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.
- 9d ago First seen · 216 lines · 53 tokens per session scan A 99a50fc9db20
tdd-workflow is a skill published in the GitHub repository mnthe/hardworker-marketplace (4 stars, last pushed 4mo ago), licensed MIT. It adds 53 tokens to every session and 1,691 once invoked, about $0.0003 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
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
iterative-development
TDD iteration loops using Claude Code Stop hooks - runs tests after each response, feeds failures back automatically.
python
Python development with ruff, mypy, pytest - TDD and type safety.
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
mobiai-mobile-tdd
You MUST use this before writing any implementation code for a mobile feature, bug fix, refactor, or behavior change. Tests come before implementation — no exceptions.