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 vanthienha199/openclaw-skills --skill deploy-kitgit clone --depth 1 https://github.com/vanthienha199/openclaw-skillsWrote 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/vanthienha199/openclaw-skills/deploy-kit)<a href="https://agentmods.dev/skills/vanthienha199/openclaw-skills/deploy-kit"><img src="https://agentmods.dev/badge/skills/vanthienha199/openclaw-skills/deploy-kit/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/vanthienha199/openclaw-skills/deploy-kit"><img src="https://agentmods.dev/badge/skills/vanthienha199/openclaw-skills/deploy-kit.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.00103 | $0.00971 |
| Opus 5 | $0.00051 | $0.00485 |
| Sonnet 5 | $0.00021 | $0.00194 |
| Haiku 4.5 | $0.00010 | $0.00097 |
Grade C, and why
deploy-kit scanned grade C with 2 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
which fly || curl -L https://fly.io/install.sh | sh Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
which fly || curl -L https://fly.io/install.sh | sh How it starts
The opening of the file, as written. The whole thing — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy Kit
You deploy projects to Vercel, Netlify, or Fly.io. One command, auto-detection, done.
Core Behavior
When the user says "deploy" or "ship", detect what kind of project it is and deploy to the best platform. If the user specifies a platform, use that one.
Auto-Detection
Check the project root for these files to determine the framework:
| File | Framework | Best Platform |
|---|---|---|
next.config.* |
Next.js | Vercel |
package.json with react-scripts |
Create React App | Vercel or Netlify |
index.html (no package.json) |
Static site | Netlify |
fly.toml |
Already configured for Fly.io | Fly.io |
Dockerfile |
Container | Fly.io |
requirements.txt or pyproject.toml |
Python | Fly.io |
Procfile |
Heroku-style | Fly.io |
astro.config.* |
Astro | Vercel or Netlify |
svelte.config.* |
SvelteKit | Vercel |
nuxt.config.* |
Nuxt | Vercel |
Deploy Commands
Vercel
# Check if vercel CLI is installed
which vercel || npm install -g vercel
# Deploy (auto-detects framework)
vercel --yes
# Deploy to production
vercel --prod --yes
Netlify
# Check if netlify CLI is installed
which netlify || npm install -g netlify-cli
# Deploy preview
netlify deploy --dir=.
# Deploy to production
netlify deploy --prod --dir=.
# For static sites, detect the build output directory:
# Next.js: out/ or .next/
# React: build/
# Plain HTML: . (current directory)
Fly.io
# Check if fly CLI is installed
which fly || curl -L https://fly.io/install.sh | sh
# If no fly.toml, launch new app
fly launch --yes --no-deploy
# Deploy
fly deploy
Workflow
Step 1: Detect
Detected: Next.js project (found next.config.js)
Recommended platform: Vercel
Step 2: Check CLI
Vercel CLI: installed (v37.2.0)
Step 3: Deploy
Run the deploy command and show the output URL.
Step 4: Report
Deployed to Vercel
URL: https://my-project-abc123.vercel.app
Production: https://my-project.vercel.app
Time: 34s
Framework: Next.js
Region: iad1 (US East)
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 · 159 lines · 103 tokens per session scan C 9a1e62930abf
deploy-kit is a skill published in the GitHub repository vanthienha199/openclaw-skills (1 stars, last pushed 5mo ago), licensed MIT. It adds 103 tokens to every session and 971 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
ship
Deploy static websites to ShipStatic. Use when the user wants to deploy a site, publish a website, upload to hosting, go live, set up a custom domain, manage deployments, or share a site URL. Free, no account needed. CLI (ship) and Node.js/browser SDK.
vercel-cli
Deploy, manage, inspect, and troubleshoot Vercel projects from the command line. Use for Vercel deployments, Vercel Toolbar comments, build failures, projects and teams, environment variables, domains and DNS, logs, metrics, Speed Insights, Core Web Vitals, request traces, usage, activity, alerts, firewall rules…
cli-ux
Use for packages/cli changes that affect command UX, prompts, help, output layout, progress, success, warnings, errors, JSON/stdout/stderr contracts, non-interactive/agent behavior, copy, or tests for those surfaces. Do not load for implementation-only refactors with unchanged CLI surface.
portaljs-deploy
Deploy a PortalJS portal to PortalJS Arc — Datopian-managed static hosting on Cloudflare. Builds a static export, uploads it, and returns a live SLUG.arc.portaljs.com URL. One command, one target. Use when a portal is ready to publish or redeploy to a live URL.
deploy-to-vercel
Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".
failure-diagnosis
Diagnose deployment failures, container crashes, and networking issues using structured pattern matching on logs and container state. Use when a deployment fails, a container crashes or exits unexpectedly, or the app is unreachable after deployment.