network-security

network-security is a skill for Claude Code from RedHatProductSecurity/prodsec-skills. It costs 43 tokens per session (2,412 once invoked), scanned A, a copy of pod-access-control, Apache-2.0.

A security guide for Kubernetes workloads, where containers run in managed groups called pods. It covers blocking host access, restricting network traffic, and declaring the ports a workload uses.

In plain words
What is it for?
Use it when writing, reviewing, or auditing Kubernetes pods, Services, NetworkPolicies, and network attachments.
Why use it?
It limits a compromised workload's ability to reach the host machine or communicate with services it does not need.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the prodsec-skills plugin — 133 skills shipped together

Good fit Use it when writing, reviewing, or auditing Kubernetes pods, Services, NetworkPolicies, and network attachments.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/redhatproductsecurity/prodsec-skills/network-security
Install

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.

Any agent
npx skills add RedHatProductSecurity/prodsec-skills --skill network-security
Clone the repo
git clone --depth 1 https://github.com/RedHatProductSecurity/prodsec-skills

Made for: Claude Code.

Or install prodsec-skills, the plugin that ships this one along with the rest of its 133 skills.

Wrote 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.

agentmods badge for network-security

README.md
[![agentmods](https://agentmods.dev/badge/skills/redhatproductsecurity/prodsec-skills/network-security/github.svg)](https://agentmods.dev/skills/redhatproductsecurity/prodsec-skills/network-security)
Your own site
<a href="https://agentmods.dev/skills/redhatproductsecurity/prodsec-skills/network-security"><img src="https://agentmods.dev/badge/skills/redhatproductsecurity/prodsec-skills/network-security/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.

agentmods 80×15 button for network-security

Your own site · 80×15
<a href="https://agentmods.dev/skills/redhatproductsecurity/prodsec-skills/network-security"><img src="https://agentmods.dev/badge/skills/redhatproductsecurity/prodsec-skills/network-security.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,412 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 88% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00043 $0.02412
Opus 5 $0.00022 $0.01206
Sonnet 5 $0.00009 $0.00482
Haiku 4.5 $0.00004 $0.00241

Measured 6d ago against content hash d84a6c5b5e8c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

network-security 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 6d 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.

Origin

This is a copy

88% identical to pod-access-control — 264 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

module/skills/network-security/SKILL.md · 209 lines

How it starts

The opening of the file, as written. The whole thing — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Network Security

Restrict host access, enforce network policies, declare all ports, and ensure connectivity across default and secondary networks.

Host Access Restrictions

Workload pods must not access host resources. All of the following must be disabled:

Required for: all profiles (mandatory)

Field Required Value
spec.hostIPC false
spec.hostNetwork false (or not set)
spec.hostPID false
spec.volumes[].hostPath Not used
spec.containers[].ports[].hostPort Not used
spec:
  hostIPC: false
  hostNetwork: false
  hostPID: false
  containers:
    - name: app
      ports:
        - containerPort: 8080

Why: Host IPC exposes inter-process communication, host network removes network isolation, host PID exposes all host processes, host path mounts expose the host filesystem, and host ports create port conflicts and bypass network controls.

Network Policies

Workload namespaces should have a default deny-all NetworkPolicy for both ingress and egress traffic. After applying the default deny, add specific policies to allow only required traffic flows.

Required for: all profiles (optional, recommended best practice)

apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: default-deny-all
  namespace: app-ns
spec:
  podSelector: {}
  policyTypes:
    - Ingress
    - Egress

Then allow specific traffic:

apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: allow-app-ingress
  namespace: app-ns
spec:
  podSelector:
    matchLabels:
      app: app
  policyTypes:
    - Ingress
  ingress:
    - from:
        - namespaceSelector:
            matchLabels:
              name: frontend-ns
      ports:
        - port: 8080
          protocol: TCP

Port Management

Declare All Container Ports

All ports a container listens on must be declared in the container spec. Platforms may block undeclared ports.

Required for: Extended (mandatory), all others (optional)

Read the full file on GitHub · 209 lines

Changes

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.

  1. 6d ago First seen · 209 lines · 43 tokens per session scan A d84a6c5b5e8c

Subscribe to this mod's changes

network-security is a skill published in the GitHub repository RedHatProductSecurity/prodsec-skills (52 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 43 tokens to every session and 2,412 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to pod-access-control, differing in 264 lines, and is treated as a copy.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens