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 echoVic/boss-skill --skill deploy-netlifygit clone --depth 1 https://github.com/echoVic/boss-skillWrote 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/echovic/boss-skill/deploy-netlify)<a href="https://agentmods.dev/skills/echovic/boss-skill/deploy-netlify"><img src="https://agentmods.dev/badge/skills/echovic/boss-skill/deploy-netlify/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/echovic/boss-skill/deploy-netlify"><img src="https://agentmods.dev/badge/skills/echovic/boss-skill/deploy-netlify.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.00032 | $0.01595 |
| Opus 5.5 | $0.00013 | $0.00638 |
| Sonnet 5.5 | $0.00006 | $0.00319 |
| Haiku 4.5 | $0.00003 | $0.00160 |
Grade A, and why
devops/deploy-netlify 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 today.
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 — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Netlify 部署
适用场景
- 前端应用(React、Vue、Svelte、Next.js)
- 静态站点(Hugo、Astro、Gatsby、Eleventy)
- Serverless Functions(Netlify Functions)
- 表单处理、身份认证(Netlify Identity)
- 边缘函数(Netlify Edge Functions)
前置条件
- 安装 Netlify CLI:
npm i -g netlify-cli - 登录 Netlify:
netlify login(需要用户交互完成授权) - 验证登录:
netlify status - 项目根目录有
package.json(Node.js 项目)
部署流程
1. 构建项目
npm run build
# 产物目录通常为 dist/、build/ 或 .next/
2. 初始化 Netlify 项目
# 在项目根目录初始化(交互式)
netlify init
# 或链接到已有项目
netlify link
netlify init 会创建 netlify.toml 配置文件。
3. netlify.toml 配置
[build]
command = "npm run build"
publish = "dist"
functions = "netlify/functions"
[build.environment]
NODE_VERSION = "20"
NPM_FLAGS = "--no-audit --no-fund"
# SPA 路由重写
[[redirects]]
from = "/*"
to = "/index.html"
status = 200
# 自定义响应头
[[headers]]
for = "/*"
[headers.values]
X-Frame-Options = "DENY"
X-XSS-Protection = "1; mode=block"
Referrer-Policy = "strict-origin-when-cross-origin"
# 边缘函数
[[edge_functions]]
function = "auth"
path = "/api/*"
4. 部署
# 预览部署(staging)
netlify deploy
# 生产部署
netlify deploy --prod
# 指定产物目录部署
netlify deploy --dir=dist --prod
部署输出示例:
Deploy path: /path/to/project/dist
Configuration: /path/to/project/netlify.toml
Deploying to main site URL...
✔ Finished hashing 32 files
✔ CDN requesting 12 files
✔ Finished uploading 12 assets
✔ Deploy is live!
Logs: https://app.netlify.com/sites/my-site/deploys/xxx
Website URL: https://my-site.netlify.app
Unique Deploy URL: https://xxx--my-site.netlify.app
5. 环境变量管理
# 设置环境变量
netlify env:set DATABASE_URL "postgres://..."
# 导入 .env 文件
netlify env:import .env
# 列出环境变量
netlify env:list
# 删除环境变量
netlify env:unset DATABASE_URL
# 拉取环境变量到本地
netlify env:pull .env
6. 域名绑定
# 添加自定义域名
netlify domains:add example.com
# 列出域名
netlify domains:list
Netlify Functions
创建 Serverless Function
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.
- today First seen · 248 lines · 32 tokens per session scan A e7f0eaf40488
devops/deploy-netlify is a skill published in the GitHub repository echoVic/boss-skill (544 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 1,595 once invoked, about $0.0001 per session on Opus 5.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-10-28.
Other skills, from other repositories
linkerd-patterns
Implement Linkerd service mesh patterns for lightweight, security-focused service mesh deployments. Use when setting up Linkerd, configuring traffic policies, or implementing zero-trust networking with minimal overhead.
cost-optimization
Optimize cloud costs across AWS, Azure, GCP, and OCI through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies.
istio-traffic-management
Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilience patterns.
convex-ship
Publish the current Convex app to a live .convex.app URL (deploy backend + upload web build).
dokploy-deploy
This skill should be used when user asks to "deploy with Dokploy", "use Dokploy Cloud", "manage self-hosted Dokploy", "deploy Docker Compose on Dokploy", "manage Dokploy databases", "configure Dokploy domains", or "look up Dokploy CLI commands".
openship-config
This skill should be used when the user asks to "create openship.json", "configure an OpenShip deployment", "make a repo deployable on OpenShip", or fix "openship config validate" errors.