Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/zebbern/claude-code-guide/pentest-checklistnpx skills add zebbern/claude-code-guide --skill pentest-checklistgit clone --depth 1 https://github.com/zebbern/claude-code-guideWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/zebbern/claude-code-guide/pentest-checklist)<a href="https://agentmods.dev/skills/zebbern/claude-code-guide/pentest-checklist"><img src="https://agentmods.dev/badge/skills/zebbern/claude-code-guide/pentest-checklist.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00057 | $0.02241 |
| Opus 5 | $0.00028 | $0.01120 |
| Sonnet 5 | $0.00011 | $0.00448 |
| Haiku 4.5 | $0.00006 | $0.00224 |
Grade A, and why
pentest-checklist scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Asks for rootlowPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo systemctl restart rsyslog Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 335 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pentest Checklist
Purpose
Provide a comprehensive checklist for planning, executing, and following up on penetration tests. Ensure thorough preparation, proper scoping, and effective remediation of discovered vulnerabilities.
Inputs/Prerequisites
- Clear business objectives for testing
- Target environment information
- Budget and timeline constraints
- Stakeholder contacts and authorization
- Legal agreements and scope documents
Outputs/Deliverables
- Defined pentest scope and objectives
- Prepared testing environment
- Security monitoring data
- Vulnerability findings report
- Remediation plan and verification
Core Workflow
Phase 1: Scope Definition
Define Objectives
- Clarify testing purpose - Determine goals (find vulnerabilities, compliance, customer assurance)
- Validate pentest necessity - Ensure penetration test is the right solution
- Align outcomes with objectives - Define success criteria
Reference Questions:
- Why are you doing this pentest?
- What specific outcomes do you expect?
- What will you do with the findings?
Know Your Test Types
| Type | Purpose | Scope |
|---|---|---|
| External Pentest | Assess external attack surface | Public-facing systems |
| Internal Pentest | Assess insider threat risk | Internal network |
| Web Application | Find application vulnerabilities | Specific applications |
| Social Engineering | Test human security | Employees, processes |
| Red Team | Full adversary simulation | Entire organization |
Enumerate Likely Threats
- Identify high-risk areas - Where could damage occur?
- Assess data sensitivity - What data could be compromised?
- Review legacy systems - Old systems often have vulnerabilities
- Map critical assets - Prioritize testing targets
Define Scope
- List in-scope systems - IPs, domains, applications
- Define out-of-scope items - Systems to avoid
- Set testing boundaries - What techniques are allowed?
- Document exclusions - Third-party systems, production data
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 335 lines · 57 tokens per session scan A 2b964e824834
pentest-checklist is a skill published in the GitHub repository zebbern/claude-code-guide (4,599 stars, last pushed today), licensed MIT. It adds 57 tokens to every session and 2,241 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
a11y-audit
../../../engineering-team/a11y-audit/skills/a11y-audit/SKILL.md.
adversarial-reviewer
../../../engineering-team/skills/adversarial-reviewer/SKILL.md.
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.
app-store-optimization
../../../marketing-skill/skills/app-store-optimization/SKILL.md.
apple-hig-expert
../../../product-team/apple-hig-expert/skills/apple-hig-expert/SKILL.md.