// Autonomous test-driven development agent that writes code to make tests pass
Proof-of-Concept (PoC) Validation Skill for security exploit verification. Use when validating exploitability of vulnerabilities, generating tailored payloads, executing exploits in sandboxed environments, or verifying successful exploitation (e.g., SQL injection, CVE exploitation, command injection). Triggers on tasks involving payload generation, exploit execution verification, sandboxed testing, or confirmation of administrative access/data exfiltration after exploitation attempts.
Module Loop and Iteration Skill for orchestrating multi-phase penetration testing workflows. Use when coordinating sequential tool execution, managing dependencies between reconnaissance and vulnerability scanning modules, implementing adaptive fallback strategies, or managing workflow state across iterations. Triggers on tasks requiring dependency chaining (e.g., Nmap results feeding into Nuclei), adaptive workflow adjustments based on results, or stateful iteration management to avoid redundant scans.
Autonomous Test-Driven Development Agent workflow for implementing features without human intervention. Use this skill when: - Implementing new features from failing tests - Fixing broken test suites - Creating production-ready code with test coverage - Working in TDD mode with minimal guidance The skill provides a 6-step autonomous loop: analyze tests → implement → predict → iterate → refactor → summarize. Works with any Python project using pytest.
Comprehensive test runner for entire Python projects. Use when: - Running all tests in a project - Discovering untested files - Generating coverage reports - Finding gaps in test coverage - Testing all modules systematically Works with pytest and generates detailed reports.
Parallel research with 4 specialized agents (Official, Practical, Edge Cases, Future)
| name | tdd-agent |
| description | Autonomous test-driven development agent that writes code to make tests pass |
| type | custom |
You are an autonomous test-driven development agent. Workflow:
Do not ask for clarification — make reasonable assumptions, document them, and proceed.
If you reach a decision point with two valid approaches, implement both as separate branches and recommend one with justification.