Skip to main content
subagent CX Codex

penetration-tester · voltagent/awesome-codex-subagents — Codex subagent: setup and overview

penetration-tester conducts adversarial security reviews across application paths, pinpointing practical attack vectors and abuse scenarios.

MIT ★ 6,505 updated 2026-10-05

Install into Codex · Manually: put the files in place All methods and platforms ↓
.codex/agents/penetration-tester.toml
Open on GitHub

What penetration-tester does

The subagent inspects entry points across authentication checks, input parameters, API interfaces, and privilege boundaries. Instead of abstract checklists, it separates verified evidence from theoretical vectors, focusing on injection weaknesses, tenant boundary breaches, session flaws, and credential leaks.

Every report breaks down the inspected scope, confirmed vulnerabilities, and the smallest remediation step needed to cut risk. The default configuration specifies the gpt-5.6-sol model.

Exploitation steps against unapproved targets are blocked unless the parent agent explicitly requests them.

What it helps with

  • map injection vectors and authorization bypass risks in updated code
  • detect credential leaks across API responses and logging outputs
  • spot rate-limiting gaps and business logic abuse flaws
  • prioritize smallest practical mitigations by actual exploitability

Example prompts for the agent

  • Run an adversarial review on the new session management endpoints
  • Inspect this API diff for tenant boundary bypass risks
  • Analyze input sanitization and potential injection vectors in this handler

How to install penetration-tester

Manually: put the files in place

.codex/agents/penetration-tester.toml

Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about penetration-tester

How to install penetration-tester in Codex?

Add the subagent configuration file to .codex/agents/penetration-tester.toml.

What is penetration-tester designed for?

It reviews code changes from an adversarial angle, validating real exploitability across API and auth boundaries.

Which model powers the penetration-tester subagent?

Its configuration specifies the gpt-5.6-sol model.

Source text

penetration-tester.toml · MIT
# penetration-tester

Use when a task needs adversarial review of an application path for exploitability, abuse cases, or practical attack surface analysis.

Own application penetration-style security review work as evidence-driven quality and risk reduction, not checklist theater.

Prioritize the smallest actionable findings or fixes that reduce user-visible failure risk, improve confidence, and preserve delivery speed.

Working mode:
1. Map the changed or affected behavior boundary and likely failure surface.
2. Separate confirmed evidence from hypotheses before recommending action.
3. Implement or recommend the minimal intervention with highest risk reduction.
4. Validate one normal path, one failure path, and one integration edge where possible.

Focus on:
- attack-surface enumeration across auth, input, API, and privilege boundaries
- exploit preconditions for injection, auth bypass, and data-exfiltration vectors
- session and token handling weaknesses enabling account compromise paths
- rate-limit, abuse-control, and business-logic abuse opportunities
- secret leakage and sensitive-data exposure in responses/logs/config
- boundary traversal risks across multi-tenant or role-scoped resources
- practical remediation prioritization by exploitability and impact

Quality checks:
- verify each finding includes attack path, prerequisites, and impact scope
- confirm severity reflects realistic exploitability, not theoretical possibility alone
- check mitigations for bypass resistance and operational feasibility
- ensure high-severity paths include immediate containment recommendations
- call out what must be validated in controlled security-testing environments

Return:
- exact scope analyzed (feature path, component, service, or diff area)
- key finding(s) or defect/risk hypothesis with supporting evidence
- smallest recommended fix/mitigation and expected risk reduction
- what was validated and what still needs runtime/environment verification
- residual risk, priority, and concrete follow-up actions

Do not provide offensive instructions for unauthorized targets or claim exploit success without evidence unless explicitly requested by the parent agent.

© VoltAgent · MIT · VoltAgent/awesome-codex-subagents

Similar subagents

All subagents for Security →

penetration-tester by other authors comes first.

penetration-tester VoltAgent Community penetration-tester runs authorized security tests, validates vulnerabilities and reports remediation steps. Use it to assess systems within an agreed scope. CX Codex 2,407installs penetration-tester rohitg00 penetration-tester is a Claude Code subagent for authorized security checks on web apps and APIs. It assesses OWASP Top 10 risks and writes findings with reproduction steps and fixes. CX Codex ★ 2,858repo stars security-pentest-planner OneWave-AI security-pentest-planner builds a penetration test plan for web applications: analyzes code, API routes, authentication and infrastructure configs, generates pentest-plan.md with concrete test cases. CX Codex +1 297installs penetration-test davila7 A slash command that runs penetration testing on a web app, API or auth flow and returns a report with fixes. CX Codex +1 434installs penetration-testing devops-skills penetration-testing walks your agent through pentest phases: recon, scanning, exploitation, reporting. Useful when you need to validate your own security controls. CX Codex +1 414installs supabase-audit-auth-users yoanbernabeu supabase-audit-auth-users is a Claude Code skill that checks Supabase Auth endpoints for user enumeration through error messages and response timing. CX Codex +1 526installs accessibility-tester VoltAgent Community The accessibility-tester subagent tests interface accessibility, WCAG conformance, and assistive technology support. Use it for audits and accessibility fixes in a project. CX Codex 346installs code-reviewer VoltAgent Community code-reviewer reviews code changes for bugs, security flaws and maintenance issues. Use it before merging complex work or auditing a project. CX Codex 31,050installs

From the same set176

The whole set →
reviewer reviewer is a Codex subagent for PR-style checks of correctness, security, regressions, and test gaps. It joins tasks that call for a focused code review. CX Codex ★ 6,505repo stars qa-expert qa-expert plans risk-based test strategies, acceptance criteria coverage, and release gating signals without checklist theater. CX Codex ★ 6,505repo stars powershell-security-hardening The powershell-security-hardening subagent reviews PowerShell safety, privileged automation, execution controls, and Windows security posture. Use it when a change needs evidence-backed hardening. CX Codex ★ 6,505repo stars performance-engineer performance-engineer — a subagent for diagnosing slow requests, critical paths, and rendering regressions. Isolates latency, memory, and database hotspots, returns minimal recommendations backed by measurement. CX Codex ★ 6,505repo stars gdpr-ccpa-compliance The gdpr-ccpa-compliance subagent reviews personal-data handling, consent flows, and data-subject rights under GDPR and CCPA/CPRA. Use it when an implementation needs a compliance check. CX Codex ★ 6,505repo stars error-detective error-detective — a subagent for fast analysis of logs, exceptions, and stack traces. Pinpoints the probable failure source by separating the primary fault from downstream cascade effects. CX Codex ★ 6,505repo stars debugger debugger isolates bugs across code paths, stack traces, and failing test runs. It pinpoints the defect and recommends a minimal fix. CX Codex ★ 6,505repo stars compliance-auditor The compliance-auditor subagent reviews controls, auditability, policy alignment, and evidence gaps in regulated workflows. CX Codex ★ 6,505repo stars

Project sponsors

Companies that keep this analytics open