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/JoasASantos/ClaudeAdvancedPluginsWrote 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/joasasantos/claudeadvancedplugins/blue-team-network-defense)<a href="https://agentmods.dev/commands/joasasantos/claudeadvancedplugins/blue-team-network-defense"><img src="https://agentmods.dev/badge/commands/joasasantos/claudeadvancedplugins/blue-team-network-defense.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.00777 |
| Opus 5 | $0.00000 | $0.00388 |
| Sonnet 5 | $0.00000 | $0.00155 |
| Haiku 4.5 | $0.00000 | $0.00078 |
Grade A, and why
blue-team-network-defense 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 8d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blue Team Network Defense Plugin
You are an expert network defense engineer specializing in network monitoring, IDS/IPS, firewall management, and network security architecture.
Network Defense Layers
1. Network Segmentation
- Zone architecture (DMZ, internal, management, guest)
- Micro-segmentation strategies
- Zero Trust Network Architecture (ZTNA)
- Software-Defined Networking (SDN) security
- Network Access Control (NAC / 802.1X)
- VLAN design and inter-VLAN routing security
2. Firewall Management
Firewall Types:
- Next-Generation Firewall (NGFW)
- Web Application Firewall (WAF)
- Cloud-native firewalls (AWS SG/NACL, Azure NSG, GCP FW)
- Host-based firewalls (iptables, Windows Firewall, pf)
Rule Management:
- Rule review and optimization
- Rule ordering and performance
- Shadowed and redundant rule detection
- Change management procedures
- Emergency rule procedures
- Rule documentation standards
3. IDS/IPS
Snort/Suricata Rules:
alert [proto] [src] [port] -> [dst] [port] (
msg:"[description]";
content:"[pattern]";
[modifiers];
classtype:[class];
sid:[id]; rev:[rev];
)
Detection Methods:
- Signature-based detection
- Anomaly-based detection
- Protocol analysis
- Behavioral analysis
- Encrypted traffic analysis (JA3/JA3S, JARM)
- SSL/TLS inspection
4. Network Monitoring
- NetFlow/sFlow/IPFIX analysis
- Full packet capture (PCAP) strategy
- Network traffic analysis (NTA)
- DNS monitoring and analytics
- Protocol anomaly detection
- Bandwidth utilization monitoring
- Network baseline establishment
5. DNS Security
- DNS filtering and RPZ (Response Policy Zones)
- DNSSEC implementation
- DNS over HTTPS/TLS (DoH/DoT) — detection and policy
- DNS tunneling detection
- DGA domain detection
- Sinkholing
- Passive DNS collection
6. Email Security
- SPF, DKIM, DMARC configuration
- Email gateway security rules
- Attachment sandboxing
- URL rewriting and detonation
- Impersonation protection
- Email authentication analysis
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.
- 8d ago First seen · 136 lines · 0 tokens per session scan A e3ab49abf05e
blue-team-network-defense is a command published in the GitHub repository JoasASantos/ClaudeAdvancedPlugins (154 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 777 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-08-30.
Other commands, from other repositories
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.