pentest-toolkit-pro-html — Claude Code skill
A skill that tells the agent how to drive an offline pentest toolkit: OWASP WSTG checklists, finding tracking, CVSS scoring and a printable report. Handy when results must live in one file.
npx skills add reason-machines/security-skills --skill pentest-toolkit-pro-html -a claude-codeWhat pentest-toolkit-pro-html does
The toolkit itself is a single HTML file you open in a browser. No build step, no dependencies. Its tabs cover rules of engagement, contract templates, mission timeline, the OWASP WSTG checklist, a findings database, a CVSS calculator, a remediation plan, report output, plus web and infrastructure cheat sheets. The skill gives the agent the map of those tabs.
Records live in browser localStorage under keys such as pentestToolkit_owaspChecklist and pentestToolkit_vulnerabilities. That keeps everything local and works without a network. It also means the data belongs to one browser profile — move it by moving the profile, and an agent in another window won't see your entries.
From the skill the agent learns how to wire a new panel through data-tab, how to extend the WSTG list with your own tests, and how to push a finding template with severity, cvss, impact and remediation fields. No API key, no server: open the file and start.
What it helps with
- run a web app through the OWASP WSTG checklist without losing track of progress
- score a finding with CVSS while the test is still running
- keep findings in a database with impact and fix notes
- produce a printable report at the end of an engagement
- extend the toolkit with a custom test or panel
Example prompts for the agent
- Open the pentesting toolkit web interface and list the OWASP WSTG items I haven't checked yet
- Add this finding to the vulnerability tracker and work out its CVSS score
- Generate a pentest report from what's currently saved in the toolkit
How to install pentest-toolkit-pro-html
1Skills CLI (Vercel)
npx skills add reason-machines/security-skills --skill pentest-toolkit-pro-html -a claude-code2Manually: put the files in place
~/.claude/skills/pentest-toolkit-pro-html/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/pentest-toolkit-pro-html/
1Skills CLI (Vercel)
npx skills add reason-machines/security-skills --skill pentest-toolkit-pro-html -a codex2Manually: put the files in place
.agents/skills/pentest-toolkit-pro-html/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add reason-machines/security-skills --skill pentest-toolkit-pro-html -a cursor2Manually: put the files in place
.cursor/skills/pentest-toolkit-pro-html/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install reason-machines/security-skills pentest-toolkit-pro-html2Manually: put the files in place
.github/skills/pentest-toolkit-pro-html/SKILL.md1Skills CLI (Vercel)
npx skills add reason-machines/security-skills --skill pentest-toolkit-pro-html -a gemini-cli2Platform CLI
gemini skills install https://github.com/reason-machines/security-skills --path skills/pentest-toolkit-pro-htmlManually: put the files in place
.devin/skills/pentest-toolkit-pro-html/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add reason-machines/security-skills --skill pentest-toolkit-pro-html -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about pentest-toolkit-pro-html
How do I install pentest-toolkit-pro-html in Claude Code?
Run npx skills add reason-machines/security-skills --skill pentest-toolkit-pro-html -a claude-code. The skill lands at ~/.claude/skills/pentest-toolkit-pro-html/SKILL.md.
What does pentest-toolkit-pro-html do?
It briefs the agent on a single-file offensive testing toolkit: WSTG checklists, finding tracking, CVSS scoring, remediation and report generation. The agent then helps you use and customise it.
Where does the toolkit keep its data?
In browser localStorage, split by key for engagement rules, contracts, timeline, the checklist, findings and the action plan. Nothing is sent to a server.