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/vuln-scan)<a href="https://agentmods.dev/commands/hermeticormus/libresecops-claude-code/vuln-scan"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/vuln-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/vuln-scan"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/vuln-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.00032 | $0.00882 |
| Opus 5.5 | $0.00013 | $0.00353 |
| Sonnet 5.5 | $0.00006 | $0.00176 |
| Haiku 4.5 | $0.00003 | $0.00088 |
Grade A, and why
vuln-scan 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/vuln-scan
Run a structured vulnerability assessment on a target, selecting appropriate tools and producing consolidated findings.
Trigger
Use this command when:
- Assessing the security posture of a codebase or infrastructure
- Running security checks as part of a deployment gate
- Performing periodic vulnerability assessments
- Evaluating a new dependency or component for known vulnerabilities
Input
Required:
- Target: Project directory, container image, or infrastructure description
Optional:
- Scan type:
code(SAST),dependencies(SCA),container,iac,cloud,secrets,all(defaults to auto-detect) - Severity threshold: Minimum severity to report (defaults to
medium) - Baseline: Path to previous scan results for delta reporting
Process
Step 1: Target Analysis
- Identify the target type from project structure and files
- Detect programming languages, frameworks, and package managers
- Identify container definitions (Dockerfile, docker-compose.yml)
- Detect infrastructure-as-code files (Terraform, CloudFormation, Kubernetes manifests)
- Map the scanning surface and determine which tool categories apply
Step 2: Tool Selection and Configuration
For each applicable scan type, select and configure tools:
Source Code (SAST):
- Semgrep with language-appropriate rulesets (p/security-audit, p/owasp, framework-specific packs)
- Language-specific linters: Bandit (Python), Brakeman (Ruby), ESLint security plugin (JavaScript), SpotBugs + FindSecBugs (Java), gosec (Go)
Dependencies (SCA):
- Parse all dependency manifests and lock files
- Check against NVD, GitHub Advisory Database, and OSV
- Identify direct vs transitive vulnerable dependencies
- Determine if vulnerable code paths are actually reachable
Container Images:
- Scan base image for OS-level vulnerabilities
- Analyze installed packages and their versions
- Check Dockerfile for security misconfigurations (running as root, exposed secrets, unnecessary packages)
- Assess image layer efficiency and attack surface
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 · +32 tokens per session 6ca07738d414
- 1mo ago First seen · 104 lines · 0 tokens per session scan A 7b0849d215e4
vuln-scan is a command published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 9d ago), licensed MIT. It adds 32 tokens to every session and 882 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
ops-k8s
Kubernetes deployment and orchestration.
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.