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/refresh-calendar)<a href="https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/refresh-calendar"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/refresh-calendar.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.00019 | $0.00984 |
| Opus 5 | $0.00010 | $0.00492 |
| Sonnet 5 | $0.00004 | $0.00197 |
| Haiku 4.5 | $0.00002 | $0.00098 |
Grade A, and why
refresh-calendar 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 8d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refresh Calendar
Cross-vendor forward-looking hardware refresh calendar: combines warranty expiration, EOL/EOS timing, and device age into a replace-now / plan-this-year / monitor plan, 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 build a calendar from. - Optional: IT Glue or Hudu, used for warranty fallback data and, where tracked, purchase-date records. Skipped with an explicit note if not connected.
Steps
-
Discover available tools. Call
conduit__search_toolsto determine which RMM connector(s) are live and their actual tool names. Never assume a specific vendor's tool surface. If a documentation platform is also connected, discover it too. -
Resolve the window. Parse
window(default12moif omitted). Accept shorthand like6mo,12mo,24mo. The window scopes the "plan this year" section — "replace now" devices are always included regardless of window, since that tier is time-independent. -
Pull device inventory, warranty data, EOL/EOS classification, and age per the
refresh-cycle-planningskill (reusing the same approach aswarranty-trackingandeol-eos-flaggingfor the first two signals), scoped to the whole portfolio. -
Tier every device into replace-now / plan-this-year / monitor, with a stated rationale citing which signal(s) drove the tier. Route devices with no resolvable signal on any input into an explicit insufficient-data bucket — never default them into monitor.
-
Lay tiered devices onto a calendar grouped by month/quarter within the requested window, attaching the specific driving date to each "plan this year" device. Call out any clustering explicitly.
-
Return the calendar, led by replace-now, then plan-this-year grouped by timing, then a monitor summary count, then the insufficient-data bucket named explicitly.
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.
- 8d ago First seen · 125 lines · 19 tokens per session scan A cdc728fb14f7
refresh-calendar is a command published in the GitHub repository WYRE-AI/msp-claude-plugins (45 stars, last pushed 5d ago), licensed Apache-2.0. It adds 19 tokens to every session and 984 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.