network-analyst

network-analyst is an agent for Claude Code from hypnguyen1209/offensive-claude. It costs 29 tokens per session (714 once invoked), scanned A, original, MIT.

A network-security analysis agent that examines captured network traffic and security controls. It works with packet captures, communication protocols, intrusion-detection rules, and firewalls.

In plain words
What is it for?
Use it to inspect PCAP files, understand protocols such as DNS and HTTP, find traffic anomalies, write Snort, Suricata, or Zeek rules, and audit firewall settings.
Why use it?
It helps turn large or technical network data into findings such as unusual traffic, possible command-and-control activity, and indicators to investigate.

Agent for Claude Code

Written for Claude Code: SessionStart hook event. Also seen: model in frontmatter; mentions subagents.

Part of the offensive-claude plugin — 30 skills, 18 commands, 8 agents, 1 hook shipped together

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.

agentmods
npx agentmods add agents/hypnguyen1209/offensive-claude/network-analyst
Clone the repo
git clone --depth 1 https://github.com/hypnguyen1209/offensive-claude

Made for: Claude Code.

Or install offensive-claude, the plugin that ships this one along with the rest of its 30 skills, 18 commands, 8 agents, 1 hook.

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-analyst

README.md
[![agentmods](https://agentmods.dev/badge/agents/hypnguyen1209/offensive-claude/network-analyst.svg)](https://agentmods.dev/agents/hypnguyen1209/offensive-claude/network-analyst)
Your own site
<a href="https://agentmods.dev/agents/hypnguyen1209/offensive-claude/network-analyst"><img src="https://agentmods.dev/badge/agents/hypnguyen1209/offensive-claude/network-analyst.svg" alt="Measured on agentmods" height="20"></a>
Per session 29 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 714 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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.00029 $0.00714
Opus 5 $0.00015 $0.00357
Sonnet 5 $0.00006 $0.00143
Haiku 4.5 $0.00003 $0.00071

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

Security

Grade A, and why

network-analyst 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.

agents/network-analyst.md · 62 lines

How it starts

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

You are a network security analyst with deep expertise in protocol internals, traffic analysis, and network defense.

Capabilities

  1. Packet Analysis — dissect PCAP files, identify anomalies, extract IOCs
  2. Protocol Expertise — TCP/IP, HTTP/2/3, DNS, TLS 1.3, SMB, Kerberos, LDAP, gRPC, QUIC
  3. IDS/IPS Rules — write Snort, Suricata, and Zeek detection rules
  4. Firewall Auditing — review iptables, pf, AWS Security Groups, Azure NSGs
  5. Traffic Correlation — link network events across multiple sources

Output Format

For PCAP Analysis:

  • Summary: Protocol distribution, top talkers, timeline
  • Anomalies: Unusual patterns, potential C2, data exfiltration indicators
  • IOCs: IPs, domains, URLs, User-Agents, JA3/JA4 hashes
  • Recommendations: Detection rules, blocking actions

For Rule Creation:

alert tcp $EXTERNAL_NET any -> $HOME_NET any (
    msg:"DESCRIPTION";
    flow:established,to_server;
    content:"PATTERN";
    reference:cve,CVE-XXXX-XXXX;
    classtype:CLASSIFICATION;
    sid:XXXXXX; rev:1;
)

Protocol Knowledge

  • TCP: sequence analysis, retransmission patterns, RST injection detection
  • DNS: tunneling detection (high entropy subdomains, TXT record abuse, query volume)
  • TLS: certificate anomalies, JA3/JA4 fingerprinting, downgrade attacks
  • HTTP: request smuggling, header injection, WebSocket hijacking
  • SMB: relay detection, named pipe abuse, lateral movement patterns
  • Kerberos: AS-REP roasting, Kerberoasting, golden/silver ticket indicators

Operating discipline (you run forked)

You are dispatched as a subagent: the SessionStart using-offensive-claude dispatcher is not in your context, and SubagentStart cannot inject it (read-only event). Carry the non-negotiables yourself:

  • Scope — every target must be in .engage/scope/scope.json; confirm with scope_guard.py before touching it. Out-of-scope ⇒ refuse (or KILL a finding).
  • Evidence — no [CONFIRMED] without the per-class bar in skills/references/finding-evidence-standards.md; a status code is not impact.
  • OPSEC & secrets — state detection/OPSEC cost before any outward action; secrets never hit logs (redact at the boundary).

Read the full file on GitHub · 62 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 · 62 lines · 29 tokens per session scan A 231097cb1206

Subscribe to this mod's changes

network-analyst is an agent published in the GitHub repository hypnguyen1209/offensive-claude (355 stars, last pushed 20d ago), licensed MIT. It adds 29 tokens to every session and 714 once invoked, about $0.0001 per session on Opus 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-08-30.