What is network-sweep?

A command that runs a cross-vendor check of network devices, connections, and topology. It turns results from connected tools such as Auvik, Meraki, and Domotz into shared health states.

Use it for portfolio-wide network health checks, including down devices, degraded links, and topology changes.

It gives a single ranked view of network problems instead of requiring separate checks in each monitoring system. It also accounts for unavailable monitoring agents when interpreting results.

network-sweep — Command for Claude Code by WYRE-AI: A command that runs a cross-vendor check of network…

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 commands/wyre-ai/msp-claude-plugins/network-sweep

Clone the repo

git clone --depth 1 https://github.com/WYRE-AI/msp-claude-plugins

Made for: Claude Code.

Or install cloudops-pack, the plugin that ships this one along with the rest of its 3 skills, 2 commands, 3 agents.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/network-sweep.svg)](https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/network-sweep)

Your own site

<a href="https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/network-sweep"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/network-sweep.svg" alt="Measured on agentmods" height="20"></a>

Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 771 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.

Model	Per session	Once invoked
Fable 5.1	$0.00021	$0.00771
Opus 5	$0.00010	$0.00385
Sonnet 5	$0.00004	$0.00154
Haiku 4.5	$0.00002	$0.00077

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

Security

Grade A, and why

network-sweep 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 2d 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.

msp-claude-plugins/cloudops-pack/commands/network-sweep.md · 104 lines

How it starts

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

Network Sweep

Cross-vendor network health sweep: devices down, degraded interfaces, and topology changes since the last sweep — pulled from whatever network-monitoring tools (Auvik, Meraki, Domotz) the org has connected through the gateway.

Prerequisites

WYRE MCP Gateway connected (conduit) with at least one network-monitoring connector. Without one, there is no network health data to report.

Steps

Discover available tools. Call conduit__search_tools to determine which network-monitoring connector(s) are live and their actual tool names (e.g. auvik__devices_list, meraki__list_networks, domotz__list_agents). Never assume a specific vendor's tool surface — resolve it fresh each run, and sweep every connected family, not just the first one found.
Check collector/agent health first (Domotz). If Domotz is connected, confirm agent status before trusting any device status behind it — an offline agent means "unknown," not "down" or "healthy," for everything it collects.
Pull device and interface status. For each connected vendor family, resolve device status into the shared taxonomy (Down / Degraded / Unknown / Healthy) per the network-health-sweep skill. Apply sustained (not momentary) error and utilization thresholds for the Degraded classification.
Pull topology-change history where available. Strongest on Auvik via configuration/audit history. Surface unplanned changes as their own section rather than silently absorbing them.
Assemble and return the report, ranked: Down → Degraded → Unknown (collector-caused) → Topology Changes → Healthy summary.

Arguments

This command takes no arguments — it always sweeps the full portfolio across whatever network-monitoring tools are connected.

Examples

Basic Usage

/cloudops-pack:network-sweep

Output

================================================================================
Network Sweep — [Date/time]
================================================================================

DOWN ([N])
--------------------------------------------------------------------------------
[device] ([vendor source], [site]) — last online [N]h ago

DEGRADED ([N])
--------------------------------------------------------------------------------
[device/interface] ([vendor source]) — [finding], threshold exceeded [N] days

UNKNOWN — COLLECTOR ISSUE ([N])
--------------------------------------------------------------------------------
[agent name] offline ([site]) — [N] devices affected, status unconfirmed

TOPOLOGY CHANGES SINCE LAST SWEEP
--------------------------------------------------------------------------------
[List of changes, or: No topology-change data available from connected sources.]

HEALTHY SUMMARY
--------------------------------------------------------------------------------
[N] devices confirmed healthy across [vendor sources]
================================================================================

Read the full file on GitHub · 104 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.

2d ago First seen · 104 lines · 21 tokens per session scan A c3a741ab4d94

Subscribe to this mod's changes

network-sweep is a command published in the GitHub repository WYRE-AI/msp-claude-plugins (44 stars, last pushed 3d ago), licensed Apache-2.0. It adds 21 tokens to every session and 771 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-09-04.

Hardware and IoT claude claude-code claude-plugins msp psa rmm

model

Check if an AI model fits on your GPU before downloading.

mitulgarg/env-doctor · 0 tokens

tapeout

Produce a complete, fab-ready export bundle for a routed board — or refuse loudly. Superset of /kct:manufacturing-readiness: runs the three sign-off pre-gates, then adds a BOM part-number-resolution gate, a per-rule warning-review gate (assembly-affecting warnings block unless explicitly acknowledged), schematic +…

rjwalters/kicad-tools · 0 tokens

network-sweep