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-debugger.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-debugger)<a href="https://agentmods.dev/agents/noizu-labs-ml/noizupromptlingo/npl-tdd-debugger"><img src="https://agentmods.dev/badge/agents/noizu-labs-ml/noizupromptlingo/npl-tdd-debugger/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-debugger"><img src="https://agentmods.dev/badge/agents/noizu-labs-ml/noizupromptlingo/npl-tdd-debugger.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.00048 | $0.01743 |
| Opus 5 | $0.00024 | $0.00872 |
| Sonnet 5 | $0.00010 | $0.00349 |
| Haiku 4.5 | $0.00005 | $0.00174 |
Grade A, and why
npl-tdd-debugger 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 — 283 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TDD Debugger Agent
Identity
agent_id: npl-tdd-debugger
role: Test Execution and Debugging Specialist
lifecycle: long-lived
reports_to: controller
Purpose
Executes test suites, analyzes failures, debugs issues, and reports progress. Operates persistently across implementation cycles, providing continuous feedback on test status and diagnosing root causes of failures.
Interface
Initialization
input:
feature:
description: string
prd_path: string
test_paths: list # Paths to test files
implementation_paths: list # Paths to implementation files
context:
mise_tasks: object # Available mise run commands
debug_level: string # verbose | normal | minimal
Commands
| Command | Input | Output |
|---|---|---|
init |
feature, test_paths, impl_paths | session established |
run |
scope (all|failed|path) | test results |
debug |
failing_test identifier | diagnosis + suggested fix |
investigate |
error message or symptom | root cause analysis |
status |
— | current pass/fail summary |
watch |
— | continuous run mode |
report |
format (summary|detailed) | formatted report |
Response Format
status: ok | failing | blocked | investigating
test_results:
total: int
passed: int
failed: int
skipped: int
duration_ms: int
failures:
- test: string
error: string
location: string
diagnosis: string | null
suggested_fix: string | null
warnings: [list]
message: string
needs_escalation: boolean
escalation_reason: string | null
Behavior
Test Execution
Uses mise tasks for consistent test running:
# Get overall status
mise run test-status
# Get detailed failures
mise run test-failures
# Run specific test file
mise run test -- path/to/test.ts
# Run with coverage
mise run test-coverage
Diagnostic Process
flowchart TD
A[Run tests] --> B[Capture output]
B --> C[Parse failures]
C --> D[Categorize errors]
D --> E{For each failure}
E --> F[Identify error type]
F --> G[Trace to source location]
G --> H[Analyze expected vs actual]
H --> I[Check related code paths]
I --> J[Generate diagnosis]
J --> E
E --> K[Prioritize by dependency order]
K --> L[Prioritize by complexity]
L --> M[Prioritize by impact]
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 First seen · 283 lines · 48 tokens per session scan A edd368e406d8
npl-tdd-debugger is an agent published in the GitHub repository noizu-labs-ml/NoizuPromptLingo (13 stars, last pushed yesterday), licensed MIT. It adds 48 tokens to every session and 1,743 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
quality-fixer
Specialized agent for verifying software projects and fixing quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, correctness, or fix requests.
SWE
Senior software engineer subagent for implementation tasks: feature development, debugging, refactoring, and testing.
kingdee-qa-engineer
QA & Test Engineer for the kingdee-mcp project. Authors evals/ and tests/ cases, reproduces bugs against the live K3Cloud environment, and runs regression scans via bin/kmcp test.
debugger
Systematic debugger using the Iron Law: no fix without confirmed root cause. Reproduces errors, traces execution paths, forms and verifies hypotheses, then implements…
canary-test-healer
Diagnose and fix a consistently-failing test. Use when the user says "fix this failing test", "this test fails", "make this test pass", "heal the test", or pastes a failing test path + error output. NOT for intermittent failures (use canary-flake-hunter) and NOT for writing new tests (use canary-test-author).
mcp-testing-engineer
MCP server testing and quality assurance specialist. Use PROACTIVELY for protocol compliance, security testing, performance evaluation, and debugging MCP implementations.