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/harden)<a href="https://agentmods.dev/commands/hermeticormus/libresecops-claude-code/harden"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/harden/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/harden"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/harden.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.00025 | $0.00887 |
| Opus 5.5 | $0.00010 | $0.00355 |
| Sonnet 5.5 | $0.00005 | $0.00177 |
| Haiku 4.5 | $0.00003 | $0.00089 |
Grade A, and why
harden 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/harden
Generate a security hardening checklist and configuration guide for a specified target platform.
Trigger
Use this command when:
- Setting up a new server, container, or cloud environment
- Preparing systems for production deployment
- Responding to a security audit finding about weak configurations
- Post-incident hardening to prevent recurrence
- Periodic security review of system configurations
Input
Required:
- Target: Platform to harden (e.g.,
ubuntu-22.04,rhel-9,docker,kubernetes,nginx,postgresql,aws,windows-server-2022)
Optional:
- Profile:
level-1(practical security) orlevel-2(defense-in-depth). Defaults tolevel-1. - Role: System role that may exclude certain controls (e.g.,
web-server,database,ci-runner,workstation) - Existing config: Path to current configuration files for delta analysis
Process
Step 1: Platform Identification
- Confirm the target platform and version
- Select the applicable CIS Benchmark or vendor hardening guide
- Determine the appropriate profile level
- Identify the system's role to filter irrelevant controls
Step 2: Control Selection
Group controls by category and priority:
Category 1: Initial Setup
- Filesystem configuration (partitioning, mount options)
- Software updates and patch management
- Bootloader configuration
- Process hardening (ASLR, DEP, core dumps)
Category 2: Services
- Disable unnecessary services
- Configure required services securely
- Remove unnecessary packages
Category 3: Network Configuration
- Firewall rules (deny by default, allow by exception)
- Network parameters (IP forwarding, source routing, ICMP redirects)
- TCP wrappers or equivalent access control
- IPv6 configuration (disable if not used)
Category 4: Logging and Auditing
- System logging configuration (syslog/journald)
- Audit system configuration (auditd/Windows Audit Policy)
- Log rotation and retention
- Log forwarding to centralized SIEM
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 · +25 tokens per session 8313ce20cfd6
- 1mo ago First seen · 121 lines · 0 tokens per session scan A 0f1f655a250a
harden is a command published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 9d ago), licensed MIT. It adds 25 tokens to every session and 887 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
extract-infrastructure
Extract Azure infrastructure and generate Docker Compose stack for local development.
deploy
Deploy an app to multiple clusters with smart placement.
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.