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 roedyrustam/vibes-plug --skill autonomous-tdd-debuggergit clone --depth 1 https://github.com/roedyrustam/vibes-plugWrote 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/roedyrustam/vibes-plug/autonomous-tdd-debugger)<a href="https://agentmods.dev/skills/roedyrustam/vibes-plug/autonomous-tdd-debugger"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/autonomous-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/skills/roedyrustam/vibes-plug/autonomous-tdd-debugger"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/autonomous-tdd-debugger.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 3 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 20 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 38 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00046 | $0.02145 |
| Opus 5.5 | $0.00018 | $0.00858 |
| Sonnet 5.5 | $0.00009 | $0.00429 |
| Haiku 4.5 | $0.00005 | $0.00215 |
Grade A, and why
autonomous-tdd-debugger scanned grade A with 1 finding 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 yesterday.
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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
import { execSync } from 'node:child_process'; How it starts
The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Autonomous TDD Debugger & Self-Healing Agent
English
Orchestration & Integration
- Test Frameworks & E2E:
e2e-testing-expert,property-mutation-testing-expert,accessibility-testing-expert - Quality Gates & Anti-Slop:
anti-slop,ai-code-review-autonomous,zero-tech-debt-auditor - Formal Verification & Contracts:
formal-spec-z3-verifier,spec-driven-development-expert - Error Resilience & Healing:
error-resilience-expert,self-healing-cloud-orchestrator,living-codebase-ast-graph - Lifecycle & Governance:
zero-to-prod-orchestrator,session-memory-manager
Description
Transforms the AI agent from a passive code generator into an active, autonomous Test-Driven Development (TDD) engineer. When invoked, the agent is mandated to execute tests, parse terminal stack traces, analyze failing assertions, and autonomously modify code in an iterative self-healing loop until all tests pass (exit code 0)—without prompting the user to manually run commands or debug errors.
Trigger Conditions
- User asks to fix failing tests or debug runtime errors without providing full error logs.
- Directives such as "Write the feature and ensure all tests pass", "Fix this bug autonomously", or "Refactor and verify".
- Phase 6 (Automated Testing & Quality Gate) execution in
zero-to-prod-orchestrator. - Post-migration regression validation in
legacy-code-translator.
Autonomous Self-Healing Loop (5-Step Protocol)
┌────────────────────────────────────────────────────────┐
│ 1. EXECUTE TEST RUNNER │
│ Run `vitest run`, `cargo test`, `pytest`, or `go test`│
└───────────────────────────┬────────────────────────────┘
│
▼
┌────────────────────────────────────────────────────────┐
│ 2. PARSE STACK TRACE & FILTER NOISE │
│ Extract failing file, line number, expected vs actual│
└───────────────────────────┬────────────────────────────┘
│
▼
┌────────────────────────────────────────────────────────┐
│ 3. AST BLAST-RADIUS CHECK │
│ Locate caller functions; isolate logic from tests │
└───────────────────────────┬────────────────────────────┘
│
▼
┌────────────────────────────────────────────────────────┐
│ 4. APPLY PRECISION PATCH │
│ Fix production implementation; NEVER mock fakes │
└───────────────────────────┬────────────────────────────┘
│
▼
┌────────────────────────────────────────────────────────┐
│ 5. RE-RUN & VERIFY (Max 5 Iterations) │
│ Exit Code 0? ──► [YES] Complete & Report Artifact │
│ └──► [NO] Loop back to Step 2 │
└────────────────────────────────────────────────────────┘
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.
- yesterday Changed · -1 lines 53626238c331
- 2d ago Changed · +1 lines 131c9682ed5a
- 5d ago Changed · +98 lines 713f7dc027cb
- 14d ago Changed 1360b0dc0d07
- 19d ago Changed 816f65954314
- 20d ago Changed 4565051d911c
- 22d ago Changed · -4 lines · +32 tokens per session a21099b83ac7
- 24d ago Changed · +6 lines · -32 tokens per session 731963c05c4a
- 1mo ago Changed fdc20a66f7bb
- 1mo ago First seen · 72 lines · 46 tokens per session scan A 8101890926d2
autonomous-tdd-debugger is a skill published in the GitHub repository roedyrustam/vibes-plug (112 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 2,145 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
test-driven-development
Drives development with tests using the red-green-refactor loop. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality. Use when asked to add tests to a function, fix a bug…
test-driven-development
Red-green-refactor cycle with meaningful coverage. Tests are written before implementation. Coverage is a side effect of good tests, not the goal.
constraint-driven-development
A development method for writing a project's quality standards as a lasting, checkable contract. It can cover areas such as test coverage, security, performance, accessibility, and architecture.
test-driven-development
Instructions for test-driven development, or TDD: writing a failing test first, then the smallest code that makes it pass, followed by cleanup.
pair-programming
AI-assisted pair programming with multiple modes (driver/navigator/switch), real-time verification, quality monitoring, and comprehensive testing. Supports TDD, debugging, refactoring, and learning sessions. Features automatic role switching, continuous code review, security scanning, and performance optimization with…
refactoring-patterns
Systematic refactoring techniques, code smell elimination, pattern extraction, and legacy modernization.