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 network-segmentationgit 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/network-segmentation)<a href="https://agentmods.dev/skills/hermeticormus/libresecops-claude-code/network-segmentation"><img src="https://agentmods.dev/badge/skills/hermeticormus/libresecops-claude-code/network-segmentation.svg" alt="Measured on agentmods" 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.02620 |
| Opus 5 | $0.00000 | $0.01310 |
| Sonnet 5 | $0.00000 | $0.00524 |
| Haiku 4.5 | $0.00000 | $0.00262 |
Grade A, and why
network-segmentation 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 4d 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 — 283 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Network Segmentation
Segmentation strategies, trust zone design, micro-segmentation, and lateral movement prevention.
Knowledge Base
Why Segmentation Matters
In a flat network (no segmentation), compromising any single host gives an attacker direct network access to every other host. Lateral movement is trivial -- the attacker can reach databases, admin panels, and other servers directly from the compromised host.
Segmentation creates boundaries that an attacker must cross. Each boundary is an opportunity for detection and prevention. The goal is to limit the blast radius of any single compromise.
Segmentation Models
| Model | Granularity | Implementation | Use Case |
|---|---|---|---|
| Perimeter | Network edge only | Edge firewall | Legacy, insufficient alone |
| Zone-based | Trust zones (DMZ, Internal, DB) | Firewalls between zones | Traditional enterprise |
| VLAN-based | Per functional group | 802.1Q VLANs + ACLs | Network-level isolation |
| Micro-segmentation | Per workload/application | Host firewalls, SDN, service mesh | Modern data center, cloud |
| Zero Trust | Per request | Identity-aware proxy, mTLS, BeyondCorp | Cloud-native, remote workforce |
Trust Zones (Classic Enterprise)
┌─────────────────────────────────┐
Internet ──────► │ DMZ (Untrusted) │
│ Web servers, reverse proxies │
└──────────────┬──────────────────┘
│ Port 8080 only
┌──────────────▼──────────────────┐
│ Application Zone │
│ App servers, API gateways │
└──────────────┬──────────────────┘
│ Port 5432 only
┌──────────────▼──────────────────┐
│ Database Zone │
│ Databases, caches │
└──────────────┬──────────────────┘
│ (No outbound)
┌──────────────▼──────────────────┐
│ Management Zone │
│ Jump boxes, monitoring, logs │
└─────────────────────────────────┘
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.
- 4d ago First seen · 283 lines · 0 tokens per session scan A 34e2a839f9ee
network-segmentation is a skill published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,620 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.