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/warranty-status)<a href="https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/warranty-status"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/warranty-status/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/warranty-status"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/warranty-status.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.00023 | $0.00880 |
| Opus 5 | $0.00012 | $0.00440 |
| Sonnet 5 | $0.00005 | $0.00176 |
| Haiku 4.5 | $0.00002 | $0.00088 |
Grade A, and why
warranty-status 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 11d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Warranty Status
Cross-vendor warranty status snapshot: expired, expiring-soon, covered, and unknown-coverage devices, pulled from whatever RMM platforms (and, as a fallback, IT Glue/Hudu) the org has connected through the gateway.
Prerequisites
- WYRE MCP Gateway connected (
conduit) with at least one RMM connector. Without an RMM, there is no device inventory to check warranty against. - Optional: IT Glue or Hudu, used as a fallback source when RMM warranty data is missing or stale. Skipped with an explicit note if not connected, not silently omitted.
Steps
-
Discover available tools. Call
conduit__search_toolsto determine which RMM connector(s) are live and their actual tool names (e.g.datto-rmm__datto_list_devices,ninjaone__list_devices,ncentral__ncentral_get_device_lifecycle). Never assume a specific vendor's tool surface. If IT Glue or Hudu is also connected, discover those too — they're a fallback source, not required. -
Resolve scope. If
clientwas provided, scope the device pull to that client/org unit/site. If omitted, run portfolio-wide across every client visible through the connected RMM(s). -
Pull device inventory and warranty data per the
warranty-trackingskill: device inventory from each connected RMM, then warranty/lifecycle fields, graded by reliability (OEM-resolved vs. manually-maintained vs. missing). -
Cross-reference documentation platforms for devices with missing or stale RMM warranty data, if IT Glue or Hudu is connected, matching by serial number or asset tag. Label any figure sourced this way.
-
Bucket every device: expired, expiring-soon (default 90-day lookahead), covered, or unknown. Never fold unknown into either extreme.
-
Return the snapshot, ranked: expired first, then expiring-soon (soonest first), then unknown (visible, not omitted), then a covered summary count.
Arguments
client(optional) — Client/org name to scope the snapshot to. Omit for a portfolio-wide snapshot across every client visible through the connected RMM(s).
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.
- 11d ago First seen · 114 lines · 23 tokens per session scan A 394a526a505f
warranty-status is a command published in the GitHub repository WYRE-AI/msp-claude-plugins (45 stars, last pushed 8d ago), licensed Apache-2.0. It adds 23 tokens to every session and 880 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-08-30.
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.