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/WYRE-AI/msp-claude-pluginsWrote 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/wyre-ai/msp-claude-plugins/network-audit)<a href="https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/network-audit"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/network-audit.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.00017 | $0.00677 |
| Opus 5 | $0.00009 | $0.00338 |
| Sonnet 5 | $0.00003 | $0.00135 |
| Haiku 4.5 | $0.00002 | $0.00068 |
Grade A, and why
network-audit 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 3d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auvik Network Audit
Walk a tenant's networks, interfaces, and configuration backups end-to-end. The output is meant to support a renewal conversation or a quarterly health check - what does the network look like, are configurations being backed up, and is anything drifting from a known-good state.
Prerequisites
- Tools:
auvik_networks_list,auvik_networks_get,auvik_interfaces_list,auvik_configurations_list,auvik_configurations_get,auvik_devices_list,auvik_entities_list_audits
Steps
-
Enumerate networks
Call
auvik_networks_listfor the tenant. Note the count, the IP ranges in use, and any networks marked private vs internet. Callauvik_networks_geton the largest few for detail (gateway, DHCP, scan status). -
List interfaces
Call
auvik_interfaces_listfor the tenant. Bucket by interface type (ethernet, wireless, virtual, etc.) and byadminStatus/operStatus. Flag any interface that is admin-up but oper-down for more than a transient period. -
Audit saved configurations
Call
auvik_configurations_listfor the tenant. For each managed network device (router, switch, firewall, accessPoint), check:- Is there at least one saved configuration? Devices with zero saved configs are a backup gap - call them out.
- When was the most recent configuration saved? Anything > 30 days old on a device that should be actively managed is stale.
-
Spot configuration drift
For devices with multiple saved configurations, call
auvik_configurations_geton the two most recent for any device that has changed in the last 7 days. Surface a one-line summary of what changed. Frequent unexpected changes on infrastructure devices warrant a conversation with the customer. -
Cross-reference with audit history
Call
auvik_entities_list_auditson the tenant or on suspect devices to surface who or what triggered recent changes - human edits, automation, or Auvik-driven actions. -
Produce the audit report
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.
- 3d ago First seen · 65 lines · 17 tokens per session scan A 1ea93212773a
network-audit is a command published in the GitHub repository WYRE-AI/msp-claude-plugins (44 stars, last pushed 4d ago), licensed Apache-2.0. It adds 17 tokens to every session and 677 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.
Other commands, from other repositories
device-info
A device-scanning command that identifies the connected chip and its VID:PID hardware identifiers. It also provides suggestions for the driver needed to use the device.
stm32-setup
Set up STM32 MCP documentation server - installs dependencies and configures your project.
get-organization-inventory-devices
Call the get-organization-inventory-devices tool from meraki-dashboard-api.
arduino-build
Compile an Arduino sketch for a target board.
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.