agentmods.dev

pwf-work-tdd

pwf-work-tdd is a command for Claude Code from J-Pster/Psters_AI_Workflow. It costs 29 tokens per session (400 once invoked), scanned A, original, MIT.

A coding workflow that uses test-driven development (TDD): write a failing test, make it pass with the smallest change, then improve the code. It runs only when tests-first work is explicitly requested.

In plain words
What is it for?
Use it to implement a requested behavior in small, tested slices, update related documentation, and prepare review and commit recommendations.
Why use it?
It gives tests-first tasks a clear cycle and keeps verification evidence for each change. It also prevents TDD from being imposed on tasks that do not need it.

Command for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter.

not rated 289repo +1 5mo ago A scan 29 tokens original MIT

Good fit Use it to implement a requested behavior in small, tested slices, update related documentation, and prepare review and commit recommendations.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/j-pster/psters_ai_workflow/pwf-work-tdd
View source ↗ J-Pster/Psters_AI_Workflow
Install

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.

Clone the repo
git clone --depth 1 https://github.com/J-Pster/Psters_AI_Workflow

Made for: Claude Code.

Wrote 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.

agentmods badge for pwf-work-tdd

README.md
[![agentmods](https://agentmods.dev/badge/commands/j-pster/psters_ai_workflow/pwf-work-tdd/github.svg)](https://agentmods.dev/commands/j-pster/psters_ai_workflow/pwf-work-tdd)
Your own site
<a href="https://agentmods.dev/commands/j-pster/psters_ai_workflow/pwf-work-tdd"><img src="https://agentmods.dev/badge/commands/j-pster/psters_ai_workflow/pwf-work-tdd/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.

agentmods 80×15 button for pwf-work-tdd

Your own site · 80×15
<a href="https://agentmods.dev/commands/j-pster/psters_ai_workflow/pwf-work-tdd"><img src="https://agentmods.dev/badge/commands/j-pster/psters_ai_workflow/pwf-work-tdd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 29 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 400 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00029 $0.00400
Opus 5 $0.00015 $0.00200
Sonnet 5 $0.00006 $0.00080
Haiku 4.5 $0.00003 $0.00040

Measured 10d ago against content hash e284060791e1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

pwf-work-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 10d 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.

plugins/psters-ai-workflow/commands/pwf-work-tdd.md · 48 lines

What it actually says

Execute Work with TDD (Opt-In)

Use this command only when tests-first delivery is explicitly requested. Apply skills/using-psters-workflow/SKILL.md at start.

Input

<work_tdd_description> #$ARGUMENTS </pwf-work_tdd_description>

If empty, ask: "What should I implement with TDD?"

Workflow

  1. Apply skills/docs-baseline-loading/SKILL.md and execute baseline loading before coding.
  2. Run /pwf-work Step 1 research discipline (docs first, context first).
  3. Apply skills/test-driven-development/SKILL.md.
  4. For each small behavior slice:
    • write failing test (Red),
    • implement minimal fix (Green),
    • refactor safely (Refactor).
  5. Keep verification evidence in each cycle.
  6. Apply skills/docs-maintenance-after-work/SKILL.md before finishing.
  7. Finish with /pwf-review and /pwf-commit-changes recommendations. Work commands update docs as part of the workflow; use /pwf-doc or /pwf-doc-capture for explicit scope-targeted documentation.

Boundaries

  • Do not force TDD on unrelated tasks.
  • Keep test scope focused on requested behavior only.

Verification Evidence Format

Use the shared evidence format from rules/operational-guardrails.mdc.

Project-specific override is allowed via docs/workflow/operational-overrides.md (if present).

  • /pwf-review after TDD cycles are complete
  • /pwf-commit-changes when review passes
Changes

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.

  1. 10d ago First seen · 48 lines · 29 tokens per session scan A e284060791e1

Subscribe to this mod's changes

pwf-work-tdd is a command published in the GitHub repository J-Pster/Psters_AI_Workflow (289 stars, last pushed 5mo ago), licensed MIT. It adds 29 tokens to every session and 400 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-30.

TDDTestingaiai-agentsworkflow
Related

Other commands, from other repositories

api-aqa-flow

Workflow for backend API test automation: TMS / Issue Tracker test cases → automated API tests, HITL-gated.

griddynamics/rosetta · 29 tokens

test-driven-development

Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first.

hamr0/agentic-toolkit · 42 tokens

bugfix

Bug fix workflow: root cause analysis → user review → regression test + fix via TDD.

nWave-ai/nWave · 18 tokens

webapp-testing

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

hamr0/agentic-toolkit · 35 tokens

usage-add

PitWay: Accumulate measured planning or qa token usage onto a milestone.

thixpin/pitway · 0 tokens

dashboard

Generar dashboard HTML local con métricas de eficiencia del proyecto SDD.

doncheli/don-cheli-sdd · 14 tokens