Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/yudefine/nuxt-supabase-starter/yudefine-deploy)<a href="https://agentmods.dev/skills/yudefine/nuxt-supabase-starter/yudefine-deploy"><img src="https://agentmods.dev/badge/skills/yudefine/nuxt-supabase-starter/yudefine-deploy/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/yudefine/nuxt-supabase-starter/yudefine-deploy"><img src="https://agentmods.dev/badge/skills/yudefine/nuxt-supabase-starter/yudefine-deploy.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.00056 | $0.05794 |
| Opus 5 | $0.00028 | $0.02897 |
| Sonnet 5 | $0.00011 | $0.01159 |
| Haiku 4.5 | $0.00006 | $0.00579 |
Grade A, and why
yudefine-deploy 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 yesterday.
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.
curl -s -X POST "https://api.cloudflare.com/client/v4/zones/${ZONE}/dns_records" \ How it starts
The opening of the file, as written. The whole thing — 369 lines — stays where its author put it; the contents beside it link to each section on GitHub.
YuDefine 部署（void.cloud / 自有 CF 雙軌）
YuDefine fleet 內兩條合法 deploy track，本 skill 兩條都支援。MUST Step 0 詢問使用者該專案走哪條，再執行對應 Step 1+。
本 skill 只規範 YuDefine fleet 政策層（compat flags hard rule、yudefine.com.tw zone DNS、CF token 來源、fleet consumer table、fleet-specific 踩坑）。
void.cloud 平台 SOP（CLI 命令、
env.ts、binding helper API、自動 migration、resource inference 等通用知識）走 officialvoidskill（<skills-root>/void/）或void mcp（search_docs/get_page/list_pages），與voidnpm package version lockstep。
Step 0 — 詢問 deploy target（必跑）
向使用者提問並等答案（見下方 § 向使用者提問）確認 deploy target，不要從專案名 / fleet 慣例直接推斷：
| 選項 | 適用 | Track |
|---|---|---|
| (A) void.cloud | 想用 void / VoidZero 平台（一鍵 deploy、自動 provision D1/R2、內建 drizzle / migration / log / domain CLI、無需自己管 CF 帳號 binding） | 走下方 Track A |
| (B) 自有 Cloudflare 帳號 | 想用 cloudflare/wrangler-action@v4 GitHub Actions 部署到自家 CF account（D1/R2 自管、wrangler.jsonc binding 明確、用 GitHub Secrets 對接） |
走下方 Track B |
MUST 把選項的取捨給使用者：
- (A) void.cloud trade-off：少寫 CI workflow、少管 binding，但鎖住 void 平台 + Vite+ 工具鏈 + 自訂網域走 cname.void.app
- (B) 自有 CF trade-off：完全控制 binding / wrangler config / deploy 流程，但要自己寫 GitHub Actions + secrets sync + D1/R2 provisioning
向使用者提問
Step 0 的提問 MUST 滿足三條，與用什麼機制問無關：
- MUST 把 (A) / (B) 兩個選項與各自的 trade-off 一併給出，NEVER 只問「要用哪個」而不給取捨
- MUST 等到明確答案才進 Track A 或 Track B；NEVER 從專案名、fleet 慣例或既有 consumer 表推斷後直接開跑
- NEVER 靜默跳過 Step 0——這一步「必跑」指的是問這件事，不是跑某個工具
這三條是義務，問法是各 runtime 自己的事。 有原生問答工具的 runtime 用它；沒有的用該 runtime 既有的使用者互動通道。NEVER 因為手上沒有某個特定工具就把這三條讀成不適用。
Fleet 現況（只是 reference，不是限制；2026-07-14 更新）：
- void.cloud（active）：
yudefine-blog（apexyudefine.com.tw）— current[email protected]、GitHub OIDC、無 legacy deploy patchco-purchase（co-purchase.void.app，未設自訂網域）— legacy[email protected]；升 current 後必須退役 patch 與長效 tokenquotation-generator（quotation.yudefine.com.tw）— legacy@void-sdk/[email protected]，待獨立 migration
- 自有 CF（wrangler-action）：
perno/nuxt-edge-agentic-rag/yuntech-usr-sroi/TDMS/nuxt-supabase-starterrental-scout（@nuxthub/core + wrangler-action；2026-05-27 仍未遷 void）
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday Changed · +2 lines 3c3d305b8ac1
- 2d ago Changed · +15 lines 5697506e9261
- 6d ago First seen · 352 lines · 56 tokens per session scan A 835769024622
yudefine-deploy is a skill published in the GitHub repository YuDefine/nuxt-supabase-starter (45 stars, last pushed today), licensed MIT. It adds 56 tokens to every session and 5,794 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-09-03.
Other skills, from other repositories
web-design
A tool for designing and publishing single-page HTML websites, such as reports, landing pages, and data displays. It uses common web libraries for layouts, charts, icons, and responsive pages, then can deploy the result to Cloudflare Pages.
nw-par-critique-dimensions
Platform design review critique dimensions and severity levels. Load when reviewing CI/CD pipelines, infrastructure, deployment strategies, observability, or security designs.
nw-deployment-strategies
Rollback procedures, risk assessment, pre/post-deployment validation, and contingency planning. Load when orchestrating deployment or preparing rollback plans. For deployment strategy details (canary, blue-green, rolling), see cicd-and-deployment skill.
nw-investigation-techniques
Evidence collection methods, problem categorization, analysis techniques, and solution design patterns.
prd-v07-implementation-loop
Execute implementation within EPICs following test-first development, continuous SoT updates, and code traceability during PRD v0.7 Build Execution. Triggers on requests to start building, implement an epic, begin coding, or when user asks "start building", "implement epic", "coding", "development", "build execution"…
prd-v08-monitoring-setup
Define monitoring strategy, metrics collection, and alerting thresholds during PRD v0.8 Deployment & Ops. Triggers on requests to set up monitoring, define alerts, or when user asks "what should we monitor?", "alerting strategy", "observability", "metrics", "SLOs", "dashboards", "monitoring setup". Outputs MON…