pentest-output-standards

Standardizes penetration testing reports, change ledgers, and negative-result documentation in Chinese.

6.2k|1.0k|Updated Nov 8, 2025
One-click install
npx skills add https://github.com/Ed1s0nZ/CyberStrikeAI --skill pentest-output-standards
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pentest-output-standards
Source: https://github.com/Ed1s0nZ/CyberStrikeAI/tree/main/skills/pentest-output-standards
Command: npx skills add https://github.com/Ed1s0nZ/CyberStrikeAI --skill pentest-output-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Penetration testing engagements often produce inconsistent reports, untracked system changes, and lost negative results, making audits and rollbacks difficult. This Skill enforces a uniform output standard so every finding, modification, and dead-end is documented in a consistent, auditable format.

Core Features & Use Cases

  • Structured Vulnerability Reports: Generates reports with severity, affected versions, exploitation steps, verified evidence, impact, and remediation advice, synchronized with record_vulnerability calls.
  • Change Ledger Tracking: Maintains a real-time ledger of every write-type change (webshells, new accounts, config edits, persistence, credential requests) with rollback commands and a one-click reverse-order rollback script.
  • Negative Result & Deadlock Handling: Records failed test methods with exclusion reasons as Facts to avoid repeated attempts, and triggers a deadlock-breaking procedure when progress stalls.
  • Use Case: During an authorized red-team engagement, the agent documents each verified vulnerability in Chinese with evidence, logs every system modification with rollback commands, and delivers a complete change ledger plus rollback script at handover.

Quick Start

Ask the agent to follow the pentest output standards when reporting findings and tracking all system changes during this authorized penetration test.

Frequently Asked Questions about pentest-output-standards

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

FAQPage Schema
How do I standardize penetration testing reports?

Use a fixed report template covering vulnerability name, severity, affected versions, exploitation conditions, request/response steps, verified evidence, impact, and remediation. This Skill enforces that structure and syncs each finding via record_vulnerability.

How to track system changes during a pentest engagement?

Maintain a real-time change ledger recording time, host, change type, location, content, and rollback command for every write-type modification. Back up configs before editing and deliver a reverse-order rollback script at handover.

What language does this Skill use for reports?

All analysis, reasoning, and reports are written in Chinese, while tool commands and code remain in English. CVE identifiers are kept in their original English form.

How are negative results handled in pentest documentation?

Each failed test is recorded with the method used, the result, and the exclusion reason, then stored as a negative-result Fact. This prevents the team from repeating the same unsuccessful attempts.

What happens when a pentest stalls with no new findings?

The deadlock-breaking procedure forces a review of all project Facts, switches attack domains or deepens hunting, and requests clarification or expanded authorization from the user when progress stalls.