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 roedyrustam/vibes-plug --skill cloud-hosting-expertgit clone --depth 1 https://github.com/roedyrustam/vibes-plugWrote 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/roedyrustam/vibes-plug/cloud-hosting-expert)<a href="https://agentmods.dev/skills/roedyrustam/vibes-plug/cloud-hosting-expert"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/cloud-hosting-expert.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.00061 | $0.02395 |
| Opus 5 | $0.00030 | $0.01197 |
| Sonnet 5 | $0.00012 | $0.00479 |
| Haiku 4.5 | $0.00006 | $0.00239 |
Grade A, and why
cloud-hosting-expert scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
async fetch(request: Request, env: Env) { How it starts
The opening of the file, as written. The whole thing — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloud Hosting Expert (2026 Edition)
English
Orchestration & Integration
Connects and orchestrates with relevant domain skills like brainstorming, zero-to-prod-orchestrator, and project-context-mapper to ensure cohesive execution.
Description
Expert guide for deploying SaaS applications and their multiple entry points (landing page, app, super admin subdomain) on modern edge and serverless platforms. Covers Vercel, Cloudflare Workers & Pages, Railway, Fly.io, and Cloudflare Workers AI for AI-powered edge workloads.
Trigger Conditions
- Deploying a Next.js, Hono, or Astro application to Vercel, Cloudflare, or Railway.
- Configuring custom domains and subdomain routing (e.g.,
app.domain.com,admin.domain.com). - Setting up Edge Middleware for multi-tenant tenant identification.
- Deploying AI inference workloads to Cloudflare Workers AI.
- Deploying long-running backend services to Railway or Fly.io.
- Implementing CDN caching strategies for SaaS applications.
Platform Selection Guide (2026)
| Platform | Best For | Free Tier | Cold Start |
|---|---|---|---|
| Vercel | Next.js, static, serverless functions | ✅ | ~200ms |
| Cloudflare Workers | Ultra-low latency APIs, edge logic | ✅ (100k req/day) | ~0ms |
| Cloudflare Pages | Static + full-stack (via Workers) | ✅ | ~0ms |
| Railway | Node.js/Go/Python long-running services, Bun | ✅ (5$/mo credit) | None |
| Fly.io | Docker containers, global distribution | ✅ (3 shared VMs) | ~500ms |
| Render | Node.js/Go/Python persistent services | ✅ (spins down) | ~30s |
Multi-Entry Point Deployment Architecture
For SaaS applications, separate deployments for each entry point:
myapp.com → Vercel (Marketing/Landing — Next.js static)
app.myapp.com → Vercel (SaaS App — Next.js dynamic)
admin.myapp.com → Vercel (Super Admin — Next.js, restricted access)
api.myapp.com → Railway/Fly.io (Backend API — long-running)
cdn.myapp.com → Cloudflare R2 (Static assets & user uploads)
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 · 251 lines · 61 tokens per session scan A 490ecfba997f
cloud-hosting-expert is a skill published in the GitHub repository roedyrustam/vibes-plug (49 stars, last pushed today), licensed MIT. It adds 61 tokens to every session and 2,395 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
shipping-and-launch
Prepares production launches. Use when preparing to deploy to production. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.
scalingo
Scalingo is a European (French) Platform-as-a-Service for deploying and operating web applications, background workers, and managed databases. Use this skill whenever the user mentions Scalingo, wants to deploy an app to Scalingo, work with the scalingo CLI, provision addons (PostgreSQL, MySQL, MongoDB, Redis…
limrun-xcode
Build an iOS / Apple app on remote Xcode with lim xcode build instead of local xcodebuild, or run its XCTest suites with lim xcode test, from any environment (Linux, Windows, macOS, VM, container). Use for non-Bazel projects (an .xcodeproj / .xcworkspace, an XcodeGen project.yml with a gitignored project, React Native…
limrun-xcode-bazel
Build a Bazel-based iOS / macOS / Apple app on Limrun's remote build execution (RBE) instead of a local Mac, and install it on a remote iOS simulator. Use when the project is a Bazel workspace (MODULE.bazel / WORKSPACE) building rulesapple / rulesswift targets and the user wants to bazel build it or run it on a…
canary-watch
Post-deploy monitoring and canary health verification.
deploy-preview
Deploy a preview branch to the staging environment for review. Use when a feature branch is ready for visual review, when someone asks to "deploy this for review", or before opening a PR.