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/zero-trust-assess)<a href="https://agentmods.dev/commands/hermeticormus/libresecops-claude-code/zero-trust-assess"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/zero-trust-assess/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/zero-trust-assess"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/zero-trust-assess.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.01126 |
| Opus 5.5 | $0.00000 | $0.00450 |
| Sonnet 5.5 | $0.00000 | $0.00225 |
| Haiku 4.5 | $0.00000 | $0.00113 |
Grade A, and why
zero-trust-assess 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 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.
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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/zero-trust-assess
Assess the current security posture against the CISA Zero Trust Maturity Model and identify the path to higher maturity levels.
Trigger
Use when you need to:
- Evaluate how close an organization or project is to zero trust principles
- Identify the highest-impact gaps in current security architecture
- Create a prioritized roadmap for zero trust adoption
- Satisfy compliance requirements that reference zero trust (NIST, FedRAMP, CMMC 2.0)
- Justify security investment with a maturity-based framework
Input
The command works through an interactive assessment across five pillars. It needs:
- Required: Willingness to answer questions about current security infrastructure, policies, and tooling across each pillar.
- Optional: Architecture diagrams, network topology, IAM configuration, existing security policies.
- Optional flag:
--pillar [identity|devices|networks|applications|data]-- assess a single pillar in depth instead of all five. - Optional flag:
--target [initial|advanced|optimal]-- specify the target maturity level for gap analysis.
Process
-
Pillar 1: Identity Assessment
- How are users authenticated? (Password-only, MFA, phishing-resistant MFA)
- Is there centralized identity management (SSO/IdP)?
- Are access policies risk-based or static?
- Is privileged access managed separately (PAM)?
- How are service-to-service identities handled?
- Is access reviewed periodically? Automated or manual?
- Score: Traditional / Initial / Advanced / Optimal
-
Pillar 2: Devices Assessment
- Is there a device inventory (all devices known)?
- Is device health assessed before granting access?
- Are unmanaged devices allowed? With what restrictions?
- Is endpoint detection and response (EDR) deployed?
- Is device posture continuously evaluated or only at login?
- Score: Traditional / Initial / Advanced / Optimal
-
Pillar 3: Networks Assessment
- Is the network flat or segmented?
- Is east-west traffic encrypted?
- Are network policies identity-aware or IP-based?
- Is DNS traffic encrypted and monitored?
- Is there micro-segmentation at the workload level?
- Are there internal resources accessible without VPN/ZTNA?
- Score: Traditional / Initial / Advanced / Optimal
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 · 137 lines · 0 tokens per session scan A 306e3a74ff02
zero-trust-assess is a command published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 11d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,126 tokens. 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
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.