Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/YuDefine/nuxt-supabase-starternpx agentmods add skills/yudefine/nuxt-supabase-starter/myWrote 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/my)<a href="https://agentmods.dev/skills/yudefine/nuxt-supabase-starter/my"><img src="https://agentmods.dev/badge/skills/yudefine/nuxt-supabase-starter/my/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/my"><img src="https://agentmods.dev/badge/skills/yudefine/nuxt-supabase-starter/my.svg" alt="Reviewed on agentmods" width="80" 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.00114 | $0.02418 |
| Opus 5 | $0.00057 | $0.01209 |
| Sonnet 5 | $0.00023 | $0.00484 |
| Haiku 4.5 | $0.00011 | $0.00242 |
Grade A, and why
my 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
\my — /decisions 的 chat 互動版本
\my 等同「列出只有我做得了的待辦」。回到電腦時問「我不在的期間，累積了哪些球在我手上的事」。
同源鐵律（2026-08-27 Charles 拍板，決策紀錄在 clade
HANDOFF.md）：\my與/decisions讀同一份佇列，兩邊都要提供該有的東西。NEVER 自己另外掃一份——同一個待拍板事項在手機上 與在對話裡長得不一樣時，人會以為那是兩件事。
MUST 依序跑四步
1. 讀佇列（NEVER 自己掃）
node ~/offline/clade/vendor/scripts/flow/flow.ts pending
Fleet 是預設（consumer repo 的問題照樣是同一個人要回的）。exit 2 = 佇列空，不是壞掉。
它已經做完五個來源的收斂——四個檔案來源（work-loop state / HANDOFF / tech-debt / tasks）
加上 spine 本身（agent 用 flow ask 直接問的題）——以及分桶、Qn 編號、和結尾那行當下實跑
的現況量測。
NEVER 改用 rg / grep 自己去翻那四個檔——它們與佇列會漂，而漂掉的那一份看起來一樣真。
spine 更是 grep 不到的：flow ask 開的題不在任何檔案裡，只有 flow pending 看得見。
spine 列入來源是 2026-08-28 Charles 對 span
65b0eaa5的拍板（carrier 已 append 進 cladeHANDOFF.md）。實作一直都讀 spine，落後的是本節原本寫「四個檔案來源」的描述——規約落後於 實作時，讀規約的人會照規約行事，而這裡的後果是 agent 以為flow ask開的題不會出現在\my，於是改用別的路徑問，那條題就真的只存在對話裡了。
2. 補第 6 個來源：只存在本 session 對話裡的待決策點
前五個來源對它們完全盲：agent 列過選項卻沒定案的、明講「這要你判斷」的、工作停在等 Charles 回答的。掃本 session 對話，每找到一條就推進佇列：
node ~/offline/clade/vendor/scripts/flow/flow.ts ask \
--question '<一句話講完，讀者沒有 scrollback>' \
--options '<選項1>,<選項2>' --recommended '<推薦那個>' \
--carrier '<TD-NNN | HANDOFF.md | tasks/xxx.md>' --actor '<你的 pane id>'
推進去才有價值：手機那側同一秒看得到，而且會推播。NEVER 只在對話裡列出來就算—— 那正是「待拍板事項多數只存在於對話裡」這個缺口本身。
選項文字只寫選項：字母前綴與「（推薦）」都由渲染端加，寫進文字會疊成 A. A. 改（推薦）（推薦）。
3. 渲染
直接用第 1 步的輸出，順序與分類不要改。需要補上下文時加在該題底下，不要重排。
第 2 步剛推進去的那幾條，MUST 在該題後面標 [本輪從對話撈出]——它們與早就登記在檔案裡的
在 flow pending 的輸出裡長得一模一樣（推進去的那一刻就都是「已登記」了），而 Charles 需要
知道哪幾條是他從沒看過的。
編號依 §QnX 協定（使用者的全域指令檔；Claude 走 ~/.claude/CLAUDE.md，其他 runtime 走各自的常駐指令檔）：只有可回答的兩類編 Qn——ruling（要我拍板）
與 review（要我驗收），兩者的編號連續跑過去，NEVER 在第二組重新從 Q1 起算。其餘三個
狀態類（不在本 repo／不可逆等外部條件／loop 推不動）一律 bullet。
review 進 Qn 是因為它符合 QnX 的准入判準——回一則短訊（通過 或 退回 + 一句理由）就結案。
NEVER 因為「它不是選擇題」把它降回 bullet：2026-08-28 之前它正是被當成狀態，7 條做完的工作
因此躺了 10.8–16.6 小時。
flow pending 已經照這條渲染——NEVER 自己替第 2 / 3 / 4 類加號碼。
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 Changed · +2 lines 0421e7588724
- 4d ago Changed · +3 lines 6f3be526ad3b
- 8d ago First seen · 115 lines · 114 tokens per session scan A 1e5336f77150
my is a skill published in the GitHub repository YuDefine/nuxt-supabase-starter (45 stars, last pushed today), licensed MIT. It adds 114 tokens to every session and 2,418 once invoked, about $0.0006 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-03.
Other skills, from other repositories
gh-issue
Size-audit, write, and split BanyanDB issues that somebody else or an automated TDD workflow can implement. Use whenever the user asks to file or revise an issue, decide whether an issue is too large, make an issue TDD-ready, turn a design into tickets, or split an umbrella into executable leaves. Do not draft or file…
nw-finalize
Archives a completed feature to docs/evolution/, migrates lasting artifacts to permanent directories, and cleans up the temporary workspace. Use after all implementation steps pass and mutation testing completes.
linear-maintenance
Bi-weekly housekeeping pass over the evlog team's Linear backlog — labels, projects, priorities, stale triage, work that is done but still open, and anything misfiled next to its siblings. Applies the mechanically verifiable fixes and surfaces the rest as decisions. Load this when the linear-maintenance schedule…
nw-new
Guided wizard to start a new feature. Asks what you want to build, recommends the right starting wave, and launches it.
nw-deliver-orchestration
DELIVER wave orchestration workflow -- 9 phases from baseline to finalization. Load when user invokes deliver command. Covers state tracking, smart skip logic, retry, resume, and quality gate enforcement.
prd-v07-test-planning
Define test cases BEFORE implementation, ensuring every API, business rule, and user journey has verifiable acceptance criteria during PRD v0.7 Build Execution. Triggers on requests to define tests, plan test coverage, create test cases, or when user asks "define tests", "test planning", "what to test?", "test cases"…