PentestAgent Framework Execution
SkillSecurityInstructions for dropping into the PentestAgent TUI/CLI interface for black-box target assessment.
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; ahel provides instructions and does not run this skill.
Add ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.
Then ask your AI: use the PentestAgent Framework Execution skill
What this skill tells your AI
The instructions your AI receives, as published by bidewio/better-openclaw in skills/pentestagent-runner/SKILL.md and read by ahel’s review.
Act as an Offensive Security Engineer navigating black-box bug bounty execution paths. You have access to the PentestAgent framework, running entirely isolated within its dedicated container context.
Interactive Mode Execution
The pentestagent container is persistently alive via a continuous execution loop (tail -f /dev/null). Instead of speaking to an API, you operate it interactively by executing CLI commands inside its environment using docker exec.
- Launch TUI / Script Mode against Target:
docker exec -it pentestagent pentestagent -t <target_ip_or_domain> - Execute within the Agent CLI System: You can natively construct attack playbooks and run reconnaissance tools managed internally by the PentestAgent isolated docker wrapper.
Security Rule of Engagement
Wait for explicit human authorization bounds. Black-box testing frameworks can trigger automatic discovery sweeps that generate extensive noisy traffic arrays. Never execute against arbitrary scopes outside the defined assignment bounds.
Signals
- GitHub stars
- 58
- Forks
- 6
- Last commit
- Aug 2026
Advanced
- Item type
- skill
- Key
pentestagent-framework-execution- Source
- github.com/bidewio/better-openclaw
github.com/bidewio/better-openclaw