sentinel-pentest

Execute authorized penetration testing workflows and hand off results to sentinel-report.

8|2|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/wangdongzuopin/sentinel-skill --skill sentinel-pentest
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sentinel-pentest
Source: https://github.com/wangdongzuopin/sentinel-skill/tree/main/skills/AuditSentry/sentinel-pentest
Command: npx skills add https://github.com/wangdongzuopin/sentinel-skill --skill sentinel-pentest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures authorized, safe, and auditable penetration testing with a formal handoff to sentinel-report upon completion.

Core Features & Use Cases

  • End-to-end authorized pentest workflow guiding engagement from scope to findings
  • Mandatory handoff to sentinel-report to generate both Markdown and HTML reports
  • Clear phase structure and governance to prevent scope creep and ensure compliance

Quick Start

Confirm authorization and scope, then follow the phase-based workflow to complete the engagement and generate the final Markdown and HTML reports.

Frequently Asked Questions about sentinel-pentest

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

FAQPage Schema
How do I execute an authorized penetration test workflow with a defined scope?

To execute an authorized penetration test workflow, you must first confirm strict authorization and engagement rules, then follow a phase-based structure covering reconnaissance, vulnerability identification, and exploitation within scope.

What is the best way to generate Markdown and HTML reports after a pentest engagement?

Generating Markdown and HTML pentest reports requires a mandatory handoff to sentinel-report, which reads its SKILL.md instructions to format and write your final engagement findings into both offline HTML and MD formats.

Why does my penetration test engagement need a formal handoff to another tool?

A penetration test engagement needs a formal handoff to ensure strict compliance, prevent scope creep, and securely transfer vulnerability findings for accurate Markdown and HTML report generation.

Can I perform exploitation during a penetration test without strict authorization rules?

No, you cannot perform exploitation without strict authorization. The workflow mandates clear scope and engagement rules before any vulnerability identification or exploitation begins to ensure safe and auditable testing.

What are the limitations of running a penetration test without a phase-based structure?

Running a penetration test without a phase-based structure risks scope creep and compliance violations, lacking the mandated governance needed to safely guide reconnaissance, exploitation, and final HTML report delivery.