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 YuDefine/nuxt-supabase-starter --skill tasksgit clone --depth 1 https://github.com/YuDefine/nuxt-supabase-starterWrote 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/tasks)<a href="https://agentmods.dev/skills/yudefine/nuxt-supabase-starter/tasks"><img src="https://agentmods.dev/badge/skills/yudefine/nuxt-supabase-starter/tasks/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/tasks"><img src="https://agentmods.dev/badge/skills/yudefine/nuxt-supabase-starter/tasks.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.00099 | $0.02310 |
| Opus 5 | $0.00049 | $0.01155 |
| Sonnet 5 | $0.00020 | $0.00462 |
| Haiku 4.5 | $0.00010 | $0.00231 |
Grade A, and why
tasks 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 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.
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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tasks Skill
tasks 是 plan-side execution planner。它不修改 truth，只把本次 plan、truth-delta 與目前 truth 轉成 /implement 可逐步執行的 tasks.md。本輪新增技術先寫 Setup；若 canonical doctor 缺失或非零，即使本輪沒有新增技術，也必須以 doctor bootstrap／repair 例外先寫 Setup；再寫 Foundational。測試層在寫產品碼之前一次對齊最新版 truth。盤點既有自動化測試只發生在寫 Phase 3 時，不得輸出成 implement task。
tasks.md 的結構產出與 doctor 驗證是兩個結果：/tasks 必須跑一次 consumer 的 canonical doctor，並交付 tasks artifact、doctor receipt 與狀態。doctor 只依目前 repo 已確認的 package manager、workspace root、技術棧與既有 check 入口決定；不得把 pnpm run doctor 當成跨 repo 預設。doctor 缺失或非零時，tasks artifact 仍可完成產出，但必須在 Setup 插入一個具名、無後續依賴且可解鎖的 bootstrap／repair task，回報真實診斷並將 doctor 標為 needs-repair 或 blocked；不得宣稱 doctor pass，也不得在 /tasks 越權實作修復。交 /implement 後先執行這個修復 task，修復 task 自己重新跑 canonical doctor，exit 0 才能 [X]。不得用 no-op、固定 exit 0 或未驗證的替代命令假裝通過。
SOP
Phase 1 -- 收斂 plan package、truth-delta 與本輪 DSL 清單
- READ 讀取使用者需求、目標 plan package 的
spec.md、plan.md、research.md、ui/**、truth-delta.md，以及受影響模組的 truth feature、模組 DSL、truth-delta 實際引用的介面根共用 DSL rows、相關 contracts/data 與specs/truth/techstack.md。 - READ 讀取
.agents/constitution/CONSTITUTION.md與.agents/constitution/shared.md，並將其中規則視為高於本地 artifact 規範的約束。 - READ 讀取
rules/TruthDelta影響盤點與任務型態判準.md，確認 ADD / MODIFY / DELETE / NOOP 如何拆到 Phase 3 測試層與 Feature 產品層，以及 Setup、Foundational 與 Test Alignment 的邊界。 - THINK 盤點本輪 Feature 用到的全部 DSL 句：含 truth-delta 有改的句，以及本輪 Feature 用到、尚無 stepdef 的句。若有
MODIFY或DELETE，同時盤點既有 stepdef、helper、fixture 與產品分支，只用來寫後續 task，不輸出獨立 phase。若任一句沒有唯一 DSL 定義，停止受影響範圍並回交/dsl-refine。
Phase 2 -- 產生 Setup 與 Foundational
- THINK 若本輪有新增技術，建立 Phase 1
Setup：寫清套件名、配置、技術環境與最後的 smoke-test；不寫 DSL 語意、不寫產品行為。 - THINK 若本輪沒有新增技術且 canonical doctor 已存在並通過，省略 Setup；若 doctor 缺失或非零，Setup 例外保留一個具名、無依賴、可解鎖的 bootstrap／repair task。不得把 helper、fixture 或落點骨架塞進 Setup。
- THINK 建立 Phase 2
Foundational：只建立後續實作程式、測試共用元件、入口、fixture、helper 與落點骨架；每則寫「只做／不做」。 - THINK Setup 與 Foundational 不得偷做 Phase 3 測試層或 Feature Green。
What ships with it
4 files 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 7e4335caf8c7
- 2d ago First seen · 76 lines · 99 tokens per session scan A aa89f02e0053
tasks is a skill published in the GitHub repository YuDefine/nuxt-supabase-starter (45 stars, last pushed today), licensed MIT. It adds 99 tokens to every session and 2,310 once invoked, about $0.0005 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-10.
Other skills, from other repositories
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-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"…
python
Python development with ruff, mypy, pytest - TDD and type safety.
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.
etl-stabilization
Phase-based orchestrator for fixing SnowConvert ETL conversion gaps in ETL-to-Snowflake migrations (SSIS, Informatica, and other platforms). Analyzes units holistically, creates a ROADMAP with test strategies, and executes fixes through phased TDD with cross-phase learning. Use when user says "fix ETL unit", "fix SSIS…
bug-fix
Regression-first TDD bug fix workflow with real tests. Use when: fixing bugs, resolving regressions, addressing runtime errors, debugging failures, or when the user reports something broken. Triggers on words like: bug, broken, error, crash, regression, not working, fix.