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/owasp-scan)<a href="https://agentmods.dev/commands/hermeticormus/libresecops-claude-code/owasp-scan"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/owasp-scan/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/owasp-scan"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/owasp-scan.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.00000 | $0.01235 |
| Opus 5.5 | $0.00000 | $0.00494 |
| Sonnet 5.5 | $0.00000 | $0.00247 |
| Haiku 4.5 | $0.00000 | $0.00123 |
Grade A, and why
owasp-scan 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 1mo 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- Command injection: `exec()`, `system()`, `child_process`, subprocess calls with user input How it starts
The opening of the file, as written. The whole thing — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/owasp-scan
Audit source code against the OWASP Top 10 (2021), producing a structured security assessment report.
Trigger
Use this command when you need a systematic security review of a web application codebase. Appropriate for:
- Pre-deployment security gates
- Code review with a security focus
- Periodic security assessments of existing applications
- Evaluating the security posture of an inherited or third-party codebase
Input
The command operates on the current project directory. Optionally accepts:
- Target scope: Specific directories or files to focus on (defaults to entire project)
- Framework hint: If auto-detection fails, specify the framework (e.g.,
django,rails,express,nextjs,spring) - Severity threshold: Minimum severity to report (
critical,high,medium,low,info). Defaults tolow.
Process
Phase 1: Reconnaissance (Stack Identification)
- Identify the programming language(s) and framework(s) from project files (
package.json,requirements.txt,Gemfile,pom.xml,go.mod, config files) - Determine the application architecture (monolith, microservices, serverless, static + API)
- Identify the template engine, ORM, authentication library, and session management approach
- Note framework version and check for known framework-level CVEs
- Map entry points: routes, controllers, API endpoints, WebSocket handlers
Phase 2: Systematic OWASP Top 10 Scan
Walk through each category in order, examining relevant code patterns:
A01:2021 - Broken Access Control
- Search for missing authorization checks on routes/endpoints
- Identify IDOR patterns (direct database ID references in URLs without ownership verification)
- Check for directory traversal in file operations
- Verify CORS configuration
- Look for privilege escalation paths (role checks, admin functions)
A02:2021 - Cryptographic Failures
- Check for hardcoded secrets, API keys, passwords in source code
- Verify password hashing algorithm (bcrypt/scrypt/argon2 vs MD5/SHA1)
- Check TLS configuration and certificate validation
- Look for sensitive data in URLs, logs, or error messages
- Verify encryption at rest for sensitive fields
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.
- 1mo ago First seen · 151 lines · 0 tokens per session scan A 1a55b1e985f7
owasp-scan is a command published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,235 tokens. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other commands, from other repositories
scout-scan
Scan a path with Scout and walk through the security findings.
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.