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 skills add HermeticOrmus/LibreSecOps-Claude-Code --skill pentest-methodologygit clone --depth 1 https://github.com/HermeticOrmus/LibreSecOps-Claude-CodeWrote 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/hermeticormus/libresecops-claude-code/pentest-methodology)<a href="https://agentmods.dev/skills/hermeticormus/libresecops-claude-code/pentest-methodology"><img src="https://agentmods.dev/badge/skills/hermeticormus/libresecops-claude-code/pentest-methodology/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/hermeticormus/libresecops-claude-code/pentest-methodology"><img src="https://agentmods.dev/badge/skills/hermeticormus/libresecops-claude-code/pentest-methodology.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00052 | $0.02159 |
| Opus 5.5 | $0.00021 | $0.00864 |
| Sonnet 5.5 | $0.00010 | $0.00432 |
| Haiku 4.5 | $0.00005 | $0.00216 |
Grade B, and why
pentest-methodology scanned grade B with 2 findings 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 12d 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.
- Privilege escalation: SUID binaries, sudo misconfiguration, kernel exploits, cron jobs, writable paths, capabilities Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Cloud metadata endpointmediumServer-side request forgery
One request to 169.254.169.254 can return temporary IAM credentials.
- Compute: Metadata service access (169.254.169.254), instance profile credentials 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Penetration Testing Methodology
Deep reference for PTES phases, OWASP Testing Guide structure, and practical testing patterns organized by technology and vulnerability class.
Knowledge Base
PTES (Penetration Testing Execution Standard)
The Penetration Testing Execution Standard defines seven phases of a penetration test:
Phase 1: Pre-engagement Interactions
- Scope definition: IP ranges, domains, applications, exclusions
- Rules of engagement: testing hours, communication channels, escalation procedures
- Authorization documentation: signed statement of work, get-out-of-jail letter
- Emergency contacts: who to call if testing causes issues
- Legal considerations: Computer Fraud and Abuse Act compliance, data protection regulations
Phase 2: Intelligence Gathering
Passive reconnaissance (no direct interaction with target):
- DNS records: A, AAAA, MX, TXT, CNAME, NS, SOA, SRV (dig, host, nslookup)
- WHOIS data: registration details, nameservers, registrar
- Search engine dorking:
site:target.com filetype:pdf,inurl:admin,intitle:"index of" - Certificate transparency logs: crt.sh, Censys for subdomain enumeration
- Public code repositories: GitHub, GitLab for exposed credentials, configuration, internal URLs
- Job postings: technology stack identification
- Social media: employee enumeration, technology hints
- Shodan/Censys: exposed services, banners, certificates
Active reconnaissance (direct interaction, within scope):
- Port scanning: Nmap SYN scan, version detection, OS fingerprinting, script scanning
- Service enumeration: Banner grabbing, protocol-specific probing
- Web application fingerprinting: Wappalyzer patterns, response headers, error pages, default files
- Directory and file discovery: ffuf, gobuster, feroxbuster with targeted wordlists
- Virtual host enumeration: Host header fuzzing for additional applications on shared infrastructure
Phase 3: Threat Modeling
- Identify valuable assets within scope
- Map trust boundaries and privilege levels
- Identify likely attack vectors based on reconnaissance
- Prioritize testing effort by risk and likelihood
- Cross-reference with STRIDE or PASTA methodologies
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.
- 12d ago Changed · +5 lines · +52 tokens per session e396d86ab951
- 1mo ago First seen · 179 lines · 0 tokens per session scan B 6835621822c3
pentest-methodology is a skill published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 9d ago), licensed MIT. It adds 52 tokens to every session and 2,159 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 2 findings (asks for root, cloud metadata endpoint). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
implementing-devsecops-security-scanning
Integrates Static Application Security Testing (SAST), Dynamic Application Security Testing (DAST), and Software Composition Analysis (SCA) into CI/CD pipelines using open-source tools. Covers Semgrep for SAST, Trivy for SCA and container scanning, OWASP ZAP for DAST, and Gitleaks for secrets detection. Activates for…
building-devsecops-pipeline-with-gitlab-ci
Design and implement a comprehensive DevSecOps pipeline in GitLab CI/CD integrating SAST, DAST, container scanning, dependency scanning, and secret detection.
integrating-dast-with-owasp-zap-in-pipeline
This skill covers integrating OWASP ZAP (Zed Attack Proxy) for Dynamic Application Security Testing in CI/CD pipelines. It addresses configuring baseline, full, and API scans against running applications, interpreting ZAP findings, tuning scan policies, and establishing DAST quality gates in GitHub Actions and GitLab…
implementing-runtime-application-self-protection
Deploy Runtime Application Self-Protection (RASP) agents to detect and block attacks from within application runtime, covering OpenRASP integration, attack pattern detection, and security policy configuration for Java and Python web applications.
integrating-dast-with-owasp-zap-in-pipeline
This skill covers integrating OWASP ZAP (Zed Attack Proxy) for Dynamic Application Security Testing in CI/CD pipelines. It addresses configuring baseline, full, and API scans against running applications, interpreting ZAP findings, tuning scan policies, and establishing DAST quality gates in GitHub Actions and GitLab…
audit-production-readiness
Audit a repository or service for release-blocking bugs, security, data/privacy, AI-agent, supply-chain, operability, and scale risks. Use for deep code audits, threat models, pre-production reviews, vulnerability triage, incidents, defensive investigation, release gates, or evidence-based 10k-to-1M-user readiness.