Agent skill · Security

recording-pentest-engagement

Package an engagement's findings, scan outputs, evidence, and signed ROE into a timestamped archive with a SHA-256 manifest covering every file. Establishes chain of custody so legal counsel, internal audit, or an outside SOC can verify the archive hasn't been modified after closeout. Optionally signs the manifest with GPG for cryptographic attestation. Use when: closing an engagement, snapshotting evidence after each scan day, before handing artifacts to customer, or after an emergency-stop event. out-of-tree path referenced in findings, unsigned manifest when signing was requested. Trigger

jeremylongshoregithub.com/jeremylongshoreGitHub ↗
claude-coderead-onlyships scriptsMIT
Install
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill recording-pentest-engagement --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 4
SKILL.md size: 8 KB
Bundled scripts: yes
Version: 3.30.0
Declared author: Jeremy Longshore <jeremy@intentsolutions.io>
Allowed tools: -Read-Bash(python3:*)-Bash(tar:*)-Bash(gpg:*)-Glob
Requires: Designed for Claude Code
Path: skills/.curated/recording-pentest-engagement/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,596
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Recording Pentest Engagement ## Overview A penetration test produces a lot of artifacts: scan outputs in multiple formats, screenshots showing the state of vulnerable pages, raw tool logs (nmap, Burp, custom scripts), the ROE and any amendments, exec-summary docs, and the findings themselves. Six months after the engagement closes, a question arises — sometimes benign ("can you remind me what we

More from claude-code-plugins-plus-skills
All skills →
About this skill
What does the recording-pentest-engagement skill do?

Package an engagement's findings, scan outputs, evidence, and signed ROE into a timestamped archive with a SHA-256 manifest covering every file. Establishes chain of custody so legal counsel, internal audit, or an outside SOC can verify the archive hasn't been modified after closeout. Optionally signs the manifest with GPG for cryptographic attestation. Use when: closing an engagement, snapshotting evidence after each scan day, before handing artifacts to customer, or after an emergency-stop event. out-of-tree path referenced in findings, unsigned manifest when signing was requested. Trigger

How do I install it?

Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill recording-pentest-engagement --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going