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 skills add WYRE-AI/msp-claude-plugins --skill refresh-cycle-planninggit 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/skills/wyre-ai/msp-claude-plugins/refresh-cycle-planning)<a href="https://agentmods.dev/skills/wyre-ai/msp-claude-plugins/refresh-cycle-planning"><img src="https://agentmods.dev/badge/skills/wyre-ai/msp-claude-plugins/refresh-cycle-planning/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/skills/wyre-ai/msp-claude-plugins/refresh-cycle-planning"><img src="https://agentmods.dev/badge/skills/wyre-ai/msp-claude-plugins/refresh-cycle-planning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00072 | $0.01972 |
| Opus 5 | $0.00036 | $0.00986 |
| Sonnet 5 | $0.00014 | $0.00394 |
| Haiku 4.5 | $0.00007 | $0.00197 |
Grade A, and why
Refresh Cycle Planning 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 10d 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refresh Cycle Planning
Overview
Most MSPs discover a hardware refresh need reactively: a device fails, or a client gets stuck on an OS that just hit end-of-support with no migration path, and the replacement conversation happens under time pressure with no budget lead time. This skill exists to move that conversation earlier — by combining three signals that are each individually useful but collectively much stronger — into a forward-looking calendar the account team can use in a quarterly business review or a capital-planning conversation, well before any of the underlying risk becomes urgent.
The three input signals, each covered by a sibling skill:
- Warranty expiration (
warranty-tracking) — when hardware coverage lapses. - EOL/EOS timing (
eol-eos-flagging) — when the OS or hardware itself stops being supported. - Device age — how long the device has been in service, pulled from RMM first-seen/enrollment date or purchase date where available.
No single signal is sufficient on its own. A device can be young with an expired warranty (a warranty that was never worth much to begin with on a low-end model), old but still fully supported and under an extended warranty, or mid-life but running an OS that's about to lose support regardless of hardware condition. This skill's job is to weigh all three together into one defensible tier per device, not to rank on whichever signal happens to be loudest.
This is not a procurement or quoting skill — it produces a planning
calendar and tiered priority list, not a purchase order. Handing the output
to a quoting/sales workflow (e.g. sales-pack) or a PSA opportunity is a
separate, deliberate next step, not something this skill does
automatically.
Anti-triggers
- ScalePad Lifecycle Manager roadmaps — LM has its own initiatives,
goals, QBR meetings, and budget forecasting; use
scalepad-lifecycle-managerrather than rebuilding its calendar here. - Pricing the replacements — use
scalepad-quoter,connectwise-cpq-quotes, orkaseya-quote-manager-quotes; this skill produces a tiered calendar and device counts, never a dollar figure.
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.
- 10d ago First seen · 177 lines · 72 tokens per session scan A 3902a04750a5
Refresh Cycle Planning is a skill published in the GitHub repository WYRE-AI/msp-claude-plugins (45 stars, last pushed 7d ago), licensed Apache-2.0. It adds 72 tokens to every session and 1,972 once invoked, about $0.0004 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 skills, from other repositories
scan-my-machine
Scans the user's actual hardware and tells them exactly which local AI models they can run, by name, with expected speed. Use when the user asks "what models can my computer run", "can I run a local LLM", "how much VRAM do I have", "which model should I download", "is my Mac good enough for local AI", "scan my…
dell-idrac-bmc-ops
Bring a Dell PowerEdge BMC (iDRAC) onto the network headlessly, standardize its baseline settings, stage its firmware, and drive an unattended Proxmox/Linux install through it — including generation-specific Redfish/racadm gotchas, the identity-before-power-action rule, and the phantom-drive failure mode caused by…
pxe-netboot
Reliable remote OS install over PXE when a server's virtual-media/remote-KVM path is broken or unreliable — proxyDHCP + TFTP via dnsmasq, kernel/initrd served over plain HTTP, and a custom-built iPXE binary with an embedded autoexec script (because a distro-packaged one won't auto-chainload). Use when a legacy BMC's…
ha-addon-scaffold
Scaffold a production-ready Home Assistant add-on: config.yaml with UI options schema, multi-arch Dockerfile + build.yaml, s6-overlay services, Ingress web UI wiring, GHCR CI, DOCS/CHANGELOG, and an add-on repository.yaml. Use when creating a new Home Assistant add-on, adding an add-on to a repository, or setting up…
automatic-cybernetic-flow-design
Use when the user wants a cybernetic flow design document for an interactive system. Specifies sensors, actuators, feedback paths, delays, and oscillation risk, and writes the design to a named local file. Not for implementing or deploying the system.
akg-agents
An agent workflow for developing, generating, testing, and tuning AKG operators. AKG is a toolkit for generating optimized computational kernels.