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 eol-eos-flagginggit 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/eol-eos-flagging)<a href="https://agentmods.dev/skills/wyre-ai/msp-claude-plugins/eol-eos-flagging"><img src="https://agentmods.dev/badge/skills/wyre-ai/msp-claude-plugins/eol-eos-flagging.svg" alt="Measured on agentmods" 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.00078 | $0.01994 |
| Opus 5 | $0.00039 | $0.00997 |
| Sonnet 5 | $0.00016 | $0.00399 |
| Haiku 4.5 | $0.00008 | $0.00199 |
Grade A, and why
EOL/EOS Flagging 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EOL/EOS Flagging
Overview
End-of-life and end-of-support are two related but distinct events. End-of-life (EOL) generally means the vendor has stopped selling or actively developing the product. End-of-support (EOS) — sometimes called end-of-extended-support — means the vendor stops shipping security patches. EOS is the harder deadline operationally: a device past EOS is accumulating unpatched vulnerabilities with no fix coming, regardless of whether it still "works." This skill flags both, keeps them distinct in the output, and prioritizes the resulting list by how much it actually matters if a given device is left running past its date.
This needs two ingredients: device inventory data (make, model, OS version, firmware version — pulled live from whatever RMM is connected) and EOL/EOS knowledge (which dates apply to which OS/hardware — general knowledge, not something the RMM exposes). The two must be combined explicitly, and the knowledge half must always carry a verification caveat, because vendor lifecycle dates do change (extended support gets purchased, timelines shift) and this skill's knowledge has a cutoff.
This is distinct from warranty-tracking: a device can be fully in
warranty and past OS end-of-support (an aging laptop still under a 5-year
warranty but running an OS version no longer patched), or out of warranty
and still fully supported (an older desktop on a current, supported OS with
no active vendor patching risk). Both signals feed refresh-cycle-planning,
but they are not the same finding and should not be conflated in a report.
Anti-triggers
- Unsupported software as a scored patch/CVE finding — an out-of-support
OS surfaced with an EPSS score and exploit maturity is vulnerability
management; use
sentinelone-vulnerabilities. - A vendor's own end-of-life field — Auvik and ScalePad both record
lifecycle/EOL data natively; use
auvik-devicesorscalepad-lifecycle-managerwhen the question is what that tool holds rather than how to rank the risk across a fleet.
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 · 185 lines · 78 tokens per session scan A 998311987b58
EOL/EOS Flagging is a skill published in the GitHub repository WYRE-AI/msp-claude-plugins (45 stars, last pushed 5d ago), licensed Apache-2.0. It adds 78 tokens to every session and 1,994 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.