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.
git 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/commands/hermeticormus/libresecops-claude-code/pentest-plan)<a href="https://agentmods.dev/commands/hermeticormus/libresecops-claude-code/pentest-plan"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/pentest-plan/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/commands/hermeticormus/libresecops-claude-code/pentest-plan"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/pentest-plan.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.00029 | $0.00919 |
| Opus 5.5 | $0.00012 | $0.00368 |
| Sonnet 5.5 | $0.00006 | $0.00184 |
| Haiku 4.5 | $0.00003 | $0.00092 |
Grade A, and why
pentest-plan scanned grade A with 0 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pentest-plan
Generate a structured penetration test plan for a defined target system or application.
Trigger
Use this command when:
- Starting a new penetration testing engagement
- Developing a test plan for a security assessment proposal
- Creating a methodology document for compliance requirements (PCI DSS 11.4, SOC 2)
- Scoping an internal security assessment
Input
Required:
- Target type:
webapp,api,network,cloud,mobile,combined - Target description: What is being tested (application name, URL, IP range, cloud account)
Optional:
- Compliance driver:
pci-dss,soc2,hipaa,fedramp,none - Constraints: Time limitations, testing windows, excluded techniques
- Prior assessments: Reference to previous test results for delta focus
Process
Step 1: Scope Definition
- Define target boundaries precisely (URLs, IP ranges, application features, API endpoints)
- Identify explicit exclusions (production data, specific hosts, denial-of-service testing)
- Define testing window and notification requirements
- Establish rules of engagement: permitted tools, techniques, and escalation procedures
- Identify emergency contacts and stop conditions
- Define data handling procedures for sensitive information encountered during testing
Step 2: Methodology Selection
Based on target type, select and customize the appropriate methodology:
Web Application:
- OWASP Testing Guide v4.2 (286 test cases across 12 categories)
- Focus areas: authentication, authorization, input validation, session management, business logic, client-side security
- Tools: Burp Suite, OWASP ZAP, Nikto, sqlmap, ffuf, nuclei
API:
- OWASP API Security Top 10 (2023)
- Focus areas: BOLA, authentication, mass assignment, rate limiting, data exposure
- Tools: Postman, Burp Suite, graphql-cop, kiterunner, arjun
Network:
- PTES Technical Guidelines
- Focus areas: service enumeration, vulnerability scanning, exploitation, lateral movement, privilege escalation
- Tools: Nmap, Nessus/OpenVAS, Metasploit, CrackMapExec, Impacket, BloodHound (AD environments)
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 · +29 tokens per session 92253623b06b
- 1mo ago First seen · 97 lines · 0 tokens per session scan A 3edef53defe6
pentest-plan is a command published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 9d ago), licensed MIT. It adds 29 tokens to every session and 919 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other commands, from other repositories
corporate-launcher
Build a secure, branded, organization-specific launcher around an AI coding CLI (Claude Code, Codex CLI, Gemini CLI, Cursor, or Cline) so the user can.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.