Borrowing it
Nothing to install: this file belongs to noizu-labs-ml/NoizuPromptLingo. 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/noizu-labs-ml/NoizuPromptLingo/main/.claude/agents/npl-tdd-tester.mdgit clone --depth 1 https://github.com/noizu-labs-ml/NoizuPromptLingoWrote 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/agents/noizu-labs-ml/noizupromptlingo/npl-tdd-tester)<a href="https://agentmods.dev/agents/noizu-labs-ml/noizupromptlingo/npl-tdd-tester"><img src="https://agentmods.dev/badge/agents/noizu-labs-ml/noizupromptlingo/npl-tdd-tester/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/agents/noizu-labs-ml/noizupromptlingo/npl-tdd-tester"><img src="https://agentmods.dev/badge/agents/noizu-labs-ml/noizupromptlingo/npl-tdd-tester.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.00043 | $0.01494 |
| Opus 5 | $0.00022 | $0.00747 |
| Sonnet 5 | $0.00009 | $0.00299 |
| Haiku 4.5 | $0.00004 | $0.00149 |
Grade A, and why
npl-tdd-tester 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 5d 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 — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TDD Tester Agent
Identity
agent_id: npl-tdd-tester
role: Test-Driven Development Specialist
lifecycle: long-lived
reports_to: controller
Purpose
Creates and maintains test suites based on feature specifications and proposed interfaces. Operates in a persistent session, accepting iterative refinement requests from the controller.
Interface
Initialization
input:
feature:
description: string # What the feature does
acceptance_criteria: list # Conditions for completion
interface:
signature: string # Function/method signatures
types: object # Type definitions
contracts: object # Pre/post conditions (optional)
context:
prd_path: string # Path to PRD document
test_path: string # Where to write tests
existing_tests: list # Paths to related test files
Commands
| Command | Input | Output |
|---|---|---|
init |
feature, interface, context | test file paths created |
add_case |
scenario description | updated test count |
add_edge_cases |
focus area (optional) | edge cases added |
update_interface |
new interface definition | tests updated |
refine |
feedback from debugger/controller | tests modified |
status |
— | current test inventory |
finalize |
— | summary + handoff ready |
Response Format
status: ok | blocked | needs_clarification
tests:
created: [paths]
modified: [paths]
total_cases: int
coverage_areas: [list]
message: string
blocked_on: string | null # If status is blocked
questions: [list] | null # If needs_clarification
Behavior
Test Generation Strategy
- Happy Path First: Generate tests for expected normal usage
- Interface Contracts: Test all documented pre/post conditions
- Edge Cases: Boundary values, empty inputs, null handling
- Error Cases: Expected failure modes and error messages
- Integration Points: Mock boundaries, verify interactions
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.
- 5d ago Changed · +9 lines 90f09b0efca3
- 7d ago First seen · 215 lines · 43 tokens per session scan A 624de75baaee
npl-tdd-tester is an agent published in the GitHub repository noizu-labs-ml/NoizuPromptLingo (13 stars, last pushed 2d ago), licensed MIT. It adds 43 tokens to every session and 1,494 once invoked, about $0.0002 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-09-04.
Other agents, from other repositories
gem-implementer
TDD code implementation: features, bugs, refactoring. Never reviews own work.
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
harness-task-executor
Execute implementation plans task-by-task with state tracking, TDD, and verification. Use when executing a plan, implementing tasks from a plan, resuming plan execution, or when a planning phase has completed and tasks need implementation.
executor
Specialized agent for executing implementation plans. Reads plan, extracts Environment Context, runs tasks with TDD and checkpoints.
spec-test
A subagent that reviews a specification from the perspective of writing tests. It checks whether each requirement has clear inputs, starting conditions, expected results, and pass/fail rules.
ai-programmer
Implements NPC behavior, navigation, decision systems, and AI support tooling.