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/attack-surface)<a href="https://agentmods.dev/commands/hermeticormus/libresecops-claude-code/attack-surface"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/attack-surface/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/attack-surface"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/attack-surface.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.00037 | $0.00997 |
| Opus 5.5 | $0.00015 | $0.00399 |
| Sonnet 5.5 | $0.00007 | $0.00199 |
| Haiku 4.5 | $0.00004 | $0.00100 |
Grade A, and why
attack-surface 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/attack-surface
Map the attack surface of a system or application, identifying all entry points, trust boundaries, data flows, and high-value targets.
Trigger
Use this command when:
- Starting a penetration test or security assessment (first step after scoping)
- Evaluating the security posture of a new or inherited system
- Preparing for a threat modeling session (attack surface feeds into threat models)
- Assessing the impact of architectural changes on security exposure
Input
Required:
- Target: Project directory, architecture description, or system documentation
Optional:
- Focus:
external(internet-facing only),internal(authenticated/internal),full(both) - Depth:
quick(entry points only),detailed(entry points + data flows + trust boundaries)
Process
Step 1: Entry Point Enumeration
Identify every point where data enters the system:
Network Layer:
- Open ports and services (from configuration files, Dockerfiles, deployment manifests)
- Load balancer and reverse proxy configurations
- DNS records and subdomains (from infrastructure-as-code)
Application Layer:
- HTTP routes and API endpoints (from code)
- GraphQL queries and mutations
- WebSocket message handlers
- File upload endpoints
- Webhook receivers
- Email processing endpoints (if applicable)
- Message queue consumers
- Scheduled job inputs (cron jobs that fetch external data)
Authentication Entry Points:
- Login forms and endpoints
- Registration flows
- Password reset mechanisms
- OAuth callback URLs
- SSO/SAML endpoints
- API key submission points
- MFA verification endpoints
Step 2: Trust Boundary Mapping
Identify where trust levels change:
- External to DMZ: Internet-facing services, WAF/CDN boundaries
- DMZ to internal: API gateways, reverse proxies, load balancers
- Service to service: Inter-service communication, service mesh boundaries
- Application to data: Database connections, cache access, file system access
- User roles: Anonymous to authenticated, user to admin, tenant to tenant
- Environment boundaries: Development to staging, staging to production
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 · +37 tokens per session e29de892b115
- 1mo ago First seen · 130 lines · 0 tokens per session scan A 8d6298ac08bf
attack-surface is a command published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 9d ago), licensed MIT. It adds 37 tokens to every session and 997 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
verify
An independent recheck of a security assessment report that derives conclusions from its own evidence instead of accepting the original findings.
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.