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/secure-review)<a href="https://agentmods.dev/commands/hermeticormus/libresecops-claude-code/secure-review"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/secure-review/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/secure-review"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/secure-review.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.00024 | $0.00815 |
| Opus 5.5 | $0.00010 | $0.00326 |
| Sonnet 5.5 | $0.00005 | $0.00163 |
| Haiku 4.5 | $0.00002 | $0.00081 |
Grade A, and why
secure-review 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/secure-review
Run a security-focused code review on provided code, identifying vulnerability patterns and producing findings with vulnerable and fixed code side by side.
Trigger
Use when reviewing code for security vulnerabilities. Appropriate for:
- Pull request security review
- Pre-deployment security checks
- Security audit of existing code
- Learning secure coding patterns by reviewing examples
- Validating that a security fix is correct and complete
Input
- Code to review: Source code files, snippets, or file paths. Can be a single function, a complete file, or multiple related files
- Language/Framework: Auto-detected from code, but specify if ambiguous
- Focus area (optional): Specific vulnerability class to focus on (e.g., "injection," "authentication," "access control"). If not specified, performs comprehensive review
- Context (optional): Application purpose, deployment environment, data sensitivity level
Process
-
Language and framework identification -- Determine the language, framework, and relevant security model (e.g., Django's built-in protections, Spring Security's filter chain)
-
Trust boundary mapping -- Identify all points where untrusted data enters the code:
- HTTP request parameters, headers, body, cookies
- Database query results (may contain attacker-controlled data)
- File contents, environment variables
- Third-party API responses
- Message queue payloads
-
Sink analysis -- Identify security-sensitive operations:
- Database queries (SQL/NoSQL injection)
- HTML/template rendering (XSS)
- Command execution (command injection)
- File operations (path traversal, arbitrary file access)
- Deserialization (RCE)
- Cryptographic operations (weak crypto)
- Authentication and authorization checks (bypass)
-
Data flow tracing -- For each source-sink pair, trace the data flow and check for:
- Proper validation at the trust boundary
- Correct encoding/escaping for the output context
- Parameterization for structured data contexts (SQL, LDAP)
- Authorization checks before sensitive operations
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 · +24 tokens per session 85405385b82e
- 1mo ago First seen · 105 lines · 0 tokens per session scan A f36f0d8f1e81
secure-review is a command published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 9d ago), licensed MIT. It adds 24 tokens to every session and 815 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.