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/cost-report)<a href="https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/cost-report"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/cost-report/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/cost-report"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/cost-report.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.00013 | $0.00901 |
| Opus 5 | $0.00006 | $0.00451 |
| Sonnet 5 | $0.00003 | $0.00180 |
| Haiku 4.5 | $0.00001 | $0.00090 |
Grade A, and why
cost-report 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 4d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cost Report
Cross-vendor cloud cost anomaly report: flags unexpected spend spikes and ranks orphaned/idle resources by reclaimable monthly cost — pulled from whatever cloud platforms (Azure, DigitalOcean) the org has connected through the gateway.
Prerequisites
- WYRE MCP Gateway connected (
conduit) with at least one cloud platform connector. Without one, there is no cost data to report.
Steps
-
Discover available tools. Call
conduit__search_toolsto determine which cloud platform connector(s) are live and their actual tool names (e.g.azure-mcp__pricing,azure-mcp__monitor,digitalocean__list_droplets,digitalocean__list_volumes,digitalocean__list_databases). Never assume a specific vendor's tool surface — cover every connected platform. -
Resolve the window. Parse
window(default30dif omitted). Accept shorthand like7d,30d,90d. Pull cost/usage data for the window and the prior comparable window. -
Correlate spend against inventory change. Flag as anomalies: spend growth with no corresponding inventory change (highest confidence), and spend growth beyond ~20% period-over-period (a stated default threshold, not tuned policy). Where itemized billing isn't exposed by a connected platform, build an inventory-based cost estimate instead and label it explicitly as an estimate.
-
Hunt for orphaned and idle resources. Across all connected platforms, check unattached storage, idle load balancers, stopped-but-still-billing compute, idle managed databases, and orphaned network resources per the
cloud-cost-managementskill. Classify each finding's confidence (confirmed idle vs. likely idle — needs confirmation). -
Rank both sections by dollar impact and return them as clearly separated findings — anomalies need investigation, reclaimable resources need a decommission decision.
Arguments
window(optional; default:30d) — Time window for the cost comparison, e.g.7d,30d,90d.
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.
- 4d ago First seen · 113 lines · 13 tokens per session scan A 8608a53aceaf
cost-report 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 13 tokens to every session and 901 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
env
Manage Vercel environment variables. Commands include list, pull, add, remove, and diff. Use to sync environment variables between Vercel and your local development environment.
deploy-to-render
Deploy the current project to Render.
storage-url
Command "storage-url" from OpenAnalystInc/10x-Team, covering command: /storage:url, usage, arguments, examples and get url for specific object.
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.
specify
Create or update the feature specification from a natural language feature description.