Automate gated penetration testing workflows across reconnaissance, enumeration, exploitation, and reporting.
npx skills add https://github.com/n4igme/randscript --skill ptest
Please help me install this Agent Skill. Skill: ptest Source: https://github.com/n4igme/randscript/tree/main/llm/skills/ptest Command: npx skills add https://github.com/n4igme/randscript --skill ptest
Structured pentest engagements often suffer from ad-hoc phase transitions, inconsistent evidence, and unrepeatable results. This Skill provides a gated, self-contained workflow to manage reconnaissance, enumeration, exploitation, and reporting with mandatory gates and artifact templates.
Initialize a new Hermes ptest engagement with default phase gates and an empty scope.
High-intent search queries and answers about installing and using this skill.
A gated penetration testing workflow enforces strict phase transitions across reconnaissance, enumeration, exploitation, and reporting. You need this for security engagements requiring auditable evidence collection, phase checklists, and repeatable attack-chain narratives to ensure compliance.
You can automate evidence collection by using a structured workflow that applies per-phase checklists and evidence templates. This ensures that phase outputs, artifacts, and time tracking are scaffolded automatically across web, network, and API targets during the penetration test.
Yes, the gated pentest workflow supports web, network, and API targets simultaneously. It manages security testing across these target types by applying uniform phase gates, artifact templates, and attack-chain framing to ensure consistent and auditable results.
The best way to structure attack-chain narratives is through a phase-driven engagement lifecycle that captures business impact and escalation paths. This approach frames remediation narratives and communicates them directly to stakeholders through structured reporting.
Yes, you can track time and artifacts automatically across penetration testing phases. The workflow enforces time tracking and generates phase-output scaffolds, ensuring that all testing artifacts are collected and auditable throughout the engagement lifecycle.
You should use a phase-driven engagement lifecycle to avoid the inconsistent evidence and unrepeatable results of ad-hoc testing. It enforces strict quality gates and artifact templates, ensuring penetration testing remains structured, auditable, and reproducible.
Kalp1774Generate a structured pentest engagement plan and initialize plan.md and session.json.
greyhaven-aiIdentify security vulnerabilities in software systems and generate remediation reports.
rajyeole6Conduct authorized penetration testing across network, web, and cloud infrastructure.
cenconq25Consolidate QA, performance, security, asset, balance, and localization verdicts into a PASS/CONCERNS/FAIL decision.
