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.
npx agentmods add commands/wyre-ai/msp-claude-plugins/device-inventorygit 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/device-inventory)<a href="https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/device-inventory"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/device-inventory.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 | $0.00017 | $0.00711 |
| Opus 5 | $0.00009 | $0.00356 |
| Sonnet 5 | $0.00003 | $0.00142 |
| Haiku 4.5 | $0.00002 | $0.00071 |
Grade A, and why
device-inventory 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 yesterday.
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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auvik Device Inventory
Produce a clean device inventory for a single Auvik tenant, broken down by device type and manage status, with lifecycle and warranty risk called out at the top. This is the workflow MSP analysts run before a QBR, a renewal, or any conversation about hardware refresh.
Prerequisites
- Auvik MCP server connected with a valid
AUVIK_USERNAMEandAUVIK_API_KEY - Tools:
auvik_tenants_list,auvik_devices_list,auvik_devices_get_details,auvik_devices_get_lifecycle,auvik_devices_get_warranty
Steps
-
Resolve the tenant
If
tenant_idwas not provided, callauvik_tenants_listand present the user the list of tenants to pick from. Do not proceed without an explicit tenant. -
Pull the device list
Call
auvik_devices_listscoped to the tenant, paginating up tolimit. The v1 list response gives youdeviceType,deviceName,manageStatus,onlineStatus,make, andmodelfor each device - enough for the headline breakdown. -
Group and count
Bucket devices by
deviceType(router, switch, firewall, accessPoint, server, workstation, printer, hypervisor, etc.) and bymanageStatus(managed,unmanaged,unknown). Surface the breakdown as a single compact table at the top of the report. -
Pull lifecycle and warranty for the long-lived gear
For devices in the infrastructure tiers (router, switch, firewall, accessPoint, server, hypervisor), call
auvik_devices_get_lifecycleandauvik_devices_get_warranty. Skip workstations and printers for this pass; their lifecycle data is rarely populated. -
Flag the risk items
Surface separately:
- Devices past end-of-sale or end-of-support per the lifecycle response
- Devices out of warranty or with warranty expiring within 90 days
- Devices with
manageStatus = unmanagedin the infrastructure tier (these are gaps - Auvik sees them but is not managing them) - Devices with
onlineStatus = offlineorunreachable
-
Produce the output
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.
- yesterday First seen · 67 lines · 17 tokens per session scan A 8dc4e3f05f80
device-inventory is a command published in the GitHub repository WYRE-AI/msp-claude-plugins (44 stars, last pushed 2d ago), licensed Apache-2.0. It adds 17 tokens to every session and 711 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
model
Check if an AI model fits on your GPU before downloading.
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 +…
device-info
扫描设备 + 自动识别芯片型号/VID:PID + 给出驱动建议.
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.