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/tenant-overview)<a href="https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/tenant-overview"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/tenant-overview/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/tenant-overview"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/tenant-overview.svg" alt="Reviewed on agentmods" width="80" 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.00016 | $0.00663 |
| Opus 5 | $0.00008 | $0.00331 |
| Sonnet 5 | $0.00003 | $0.00133 |
| Haiku 4.5 | $0.00002 | $0.00066 |
Grade A, and why
tenant-overview 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 5d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auvik Tenant Overview
Produce a one-page snapshot for a single Auvik-monitored client. Designed as the first command an analyst runs when picking up a ticket for an unfamiliar tenant - establishes scale, health, and current pain in under a screen of output.
Prerequisites
- Tools:
auvik_tenants_get,auvik_tenants_detail,auvik_devices_list,auvik_alerts_list,auvik_networks_list,auvik_billing_client_usage,auvik_billing_device_usage
Steps
-
Tenant header
Call
auvik_tenants_getandauvik_tenants_detailfor descriptive metadata - name, status, region, contact, contract type if exposed. -
Device count and breakdown
Call
auvik_devices_listwith a high page size and accumulate. Report total device count and the top device-type buckets (router, switch, firewall, accessPoint, server, workstation, printer, other). -
Open alert count
Call
auvik_alerts_listwithstatus=open. Report counts per severity (emergency / critical / warning / info). Highlight if any emergency or critical alerts are open. -
Network footprint
Call
auvik_networks_list. Report network count and whether scans are healthy (any networks in error or unscanned state). -
Billing usage
Call
auvik_billing_client_usagefor the tenant for the current billing period andauvik_billing_device_usagefor the breakdown. Report the billable device count and any growth vs the previous period if available. -
Output format
A compact card-style report:
Tenant: <name> Region: <region> Status: <status> Devices: <N> (routers <a>, switches <b>, firewalls <c>, APs <d>, servers <e>, ...) Networks: <N> Open alerts: emergency <e> / critical <c> / warning <w> / info <i> Billable devices: <N> Period: <YYYY-MM>Below the card, a 3-5 bullet "what to look at next" list referencing the relevant deeper commands (
/auvik:alert-triage,/auvik:device-inventory,/auvik:network-audit,/auvik:capacity-check).
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.
- 5d ago First seen · 68 lines · 16 tokens per session scan A 3a32e15ad131
tenant-overview is a command published in the GitHub repository WYRE-AI/msp-claude-plugins (45 stars, last pushed 6d ago), licensed Apache-2.0. It adds 16 tokens to every session and 663 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.