pentest-agent-authorization

Enforce proof-backed consent and scope validation before security assessment command execution.

Updated Jul 30, 2026

Search Tags:#workflow #authorization #security #audit #compliance #pentest

Ready to run

npx skills add https://github.com/salmanabdurrahman/pi-pentest-agent --skill pentest-agent-authorization

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pentest-agent-authorization
Source: https://github.com/salmanabdurrahman/pi-pentest-agent/tree/main/skills/pentest-agent-authorization
Command: npx skills add https://github.com/salmanabdurrahman/pi-pentest-agent --skill pentest-agent-authorization

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the challenge of maintaining strict legal and operational compliance during security assessments by enforcing a mandatory authorization gate, preventing unauthorized testing, and ensuring all actions are backed by verified consent and scope.

Core Features & Use Cases

Authorization Lifecycle Management: Records proof metadata, manages target-hash caches, and enforces a strict consent state machine.
Preflight Gate Enforcement: Automatically validates scope, consent, and risk approval before any active tool execution or command invocation.
Multi-Engagement Contexts: Safely isolates authorization caches and evidence for different targets, preventing cross-engagement contamination.

Quick Start

Use the pentest-agent-authorization skill to record the proof metadata and initialize the authorization cache for the target defined in the current scope file.

Frequently Asked Questions about pentest-agent-authorization

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enforce proof-backed authorization for penetration testing?▼

To enforce proof-backed authorization for penetration testing, you must pass cryptographic hashes for targets, proof, and scope through a fail-closed gate before any command execution begins.

What is a fail-closed architecture in pentest workflow management?▼

A fail-closed architecture in pentest workflow management requires valid cryptographic hashes for targets, proof, and scope before enabling command execution, preventing unauthorized security testing.

How do I prevent cross-engagement contamination during security assessments?▼

To prevent cross-engagement contamination during security assessments, isolate authorization caches and evidence for different targets, ensuring each active testing context remains strictly separated.

Does this authorization lifecycle management approach support diverse engagement modes?▼

This authorization lifecycle management approach supports diverse engagement modes by safely isolating authorization caches across different targets while enforcing strict scope validation gates.

How do I validate scope and consent before active tool execution?▼

To validate scope and consent before active tool execution, a preflight gate automatically checks risk approval, consent state, and scope boundaries to ensure compliant testing.

Why do I need cryptographic hashes for security assessment compliance?▼

You need cryptographic hashes for security assessment compliance because the fail-closed architecture requires valid hashes for targets, proof, and scope to maintain strict legal boundaries.