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.
npx skills add HermeticOrmus/LibreSecOps-Claude-Code --skill zero-trust-principlesgit 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/skills/hermeticormus/libresecops-claude-code/zero-trust-principles)<a href="https://agentmods.dev/skills/hermeticormus/libresecops-claude-code/zero-trust-principles"><img src="https://agentmods.dev/badge/skills/hermeticormus/libresecops-claude-code/zero-trust-principles/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/skills/hermeticormus/libresecops-claude-code/zero-trust-principles"><img src="https://agentmods.dev/badge/skills/hermeticormus/libresecops-claude-code/zero-trust-principles.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.02121 |
| Opus 5.5 | $0.00000 | $0.00848 |
| Sonnet 5.5 | $0.00000 | $0.00424 |
| Haiku 4.5 | $0.00000 | $0.00212 |
Grade A, and why
zero-trust-principles 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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Zero Trust Principles
NIST SP 800-207 reference knowledge, core tenets, deployment models, and the theoretical foundation of zero trust architecture.
Knowledge Base
NIST SP 800-207 Core Tenets
NIST defines seven tenets of zero trust:
-
All data sources and computing services are considered resources. A network is not just servers -- laptops, phones, SaaS applications, IoT devices, and cloud functions are all resources that need protection.
-
All communication is secured regardless of network location. Internal network traffic is not inherently more trustworthy than external traffic. Encrypt and authenticate all communication.
-
Access to individual enterprise resources is granted on a per-session basis. Trust is not persistent. Each access request is evaluated independently based on current context.
-
Access to resources is determined by dynamic policy. Policies consider identity, device state, behavioral patterns, and environmental attributes -- not just static role assignments.
-
The enterprise monitors and measures the integrity and security posture of all owned and associated assets. No device is trusted by default. Device health, patch level, and configuration are continuously evaluated.
-
All resource authentication and authorization are dynamic and strictly enforced before access is allowed. Authentication is not a one-time gate. It is a continuous process that responds to changing risk signals.
-
The enterprise collects as much information as possible about the current state of assets, network infrastructure, and communications and uses it to improve its security posture. Visibility is not optional. You cannot enforce zero trust without comprehensive telemetry.
Logical Components (NIST SP 800-207)
Policy Engine (PE): The brain. Makes the access decision based on policy, identity, device state, threat intelligence, and behavioral analytics.
Policy Administrator (PA): Executes the PE's decision by instructing the enforcement point to allow or deny access. May generate session-specific credentials (tokens, certificates).
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 · 186 lines · 0 tokens per session scan A 1ae22f633728
zero-trust-principles is a skill 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 2,121 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 skills, from other repositories
implementing-devsecops-security-scanning
Integrates Static Application Security Testing (SAST), Dynamic Application Security Testing (DAST), and Software Composition Analysis (SCA) into CI/CD pipelines using open-source tools. Covers Semgrep for SAST, Trivy for SCA and container scanning, OWASP ZAP for DAST, and Gitleaks for secrets detection. Activates for…
building-devsecops-pipeline-with-gitlab-ci
Design and implement a comprehensive DevSecOps pipeline in GitLab CI/CD integrating SAST, DAST, container scanning, dependency scanning, and secret detection.
integrating-dast-with-owasp-zap-in-pipeline
This skill covers integrating OWASP ZAP (Zed Attack Proxy) for Dynamic Application Security Testing in CI/CD pipelines. It addresses configuring baseline, full, and API scans against running applications, interpreting ZAP findings, tuning scan policies, and establishing DAST quality gates in GitHub Actions and GitLab…
implementing-runtime-application-self-protection
Deploy Runtime Application Self-Protection (RASP) agents to detect and block attacks from within application runtime, covering OpenRASP integration, attack pattern detection, and security policy configuration for Java and Python web applications.
integrating-dast-with-owasp-zap-in-pipeline
This skill covers integrating OWASP ZAP (Zed Attack Proxy) for Dynamic Application Security Testing in CI/CD pipelines. It addresses configuring baseline, full, and API scans against running applications, interpreting ZAP findings, tuning scan policies, and establishing DAST quality gates in GitHub Actions and GitLab…
audit-production-readiness
Audit a repository or service for release-blocking bugs, security, data/privacy, AI-agent, supply-chain, operability, and scale risks. Use for deep code audits, threat models, pre-production reviews, vulnerability triage, incidents, defensive investigation, release gates, or evidence-based 10k-to-1M-user readiness.