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/wtWrote 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/wt)<a href="https://agentmods.dev/skills/yudefine/nuxt-supabase-starter/wt"><img src="https://agentmods.dev/badge/skills/yudefine/nuxt-supabase-starter/wt.svg" alt="Measured on agentmods" 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.00060 | $0.05991 |
| Opus 5 | $0.00030 | $0.02995 |
| Sonnet 5 | $0.00012 | $0.01198 |
| Haiku 4.5 | $0.00006 | $0.00599 |
Grade A, and why
wt 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 — 387 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/wt — orchestrate worktree task lifecycle
/wt is the single entry point for "do work in a worktree". It builds the worktree, auto-routes the executor (Pi astra/luna for non-UI coding/analysis/debug, Claude subagent only for the Form 3/4 cases — see Step 1.8; UI view implementation is never dispatched at all), and reports — without squashing or cleaning up. The worktree branch holds committed work through OPSX verification and archive. The coordinator then follows [[worktree-default.commit-ceremony]] to merge one worktree and immediately commit its scoped result on main.
This deferred-landing model guarantees main never carries half-done features between sessions: only fully-reviewed-and-archived changes touch main. The previous v2.0 behavior — /wt return time squash + cleanup — accumulated cross-session WIP in main and made /commit impossible whenever the 人工檢查 Gate triggered.
The user's only follow-up action is the actual 人工檢查 decision（GUI 的 OK / Issue / Skip）。After that decision, the coordinator completes OPSX archive in the implementation worktree, commits bookkeeping, then performs merge-back and /commit itself. If the landing ceremony requires a separate clean session, use [[session-tasks.operations]] § Herdr session transport and return the dispatch receipt; NEVER ask the user to open main or type either invocation.
When to invoke
Whenever a coding task (write, edit, refactor, migration prep) or investigation task (analysis, debugging, auditing) is about to start from the main worktree. /wt makes per-task worktree isolation cheap; the previous "type a slug, copy a oneliner, open a new session" choreography is gone.
Non-UI tasks are automatically routed to Pi (cheaper, doesn't consume Claude context); UI tasks stay with Claude subagent. Use --claude or --pi (the older --codex spelling is still accepted) to override.
Do not invoke /wt in these cases:
What ships with it
3 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.
- today Changed · -2 lines · -4 tokens per session 9baa4ed3fd01
- 3d ago First seen · 389 lines · 64 tokens per session scan A 375ba4b0e4bb
wt is a skill published in the GitHub repository YuDefine/nuxt-supabase-starter (45 stars, last pushed yesterday), licensed MIT. It adds 60 tokens to every session and 5,991 once invoked, about $0.0003 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
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.
nw-hotspot
Git change frequency hotspot analysis — find the most-changed files in your codebase.
nw-mikado
Wave: CROSSWAVE Agent: Crafty (nw-software-crafter) Command: mikado.
nw-par-review-criteria
Quality dimensions and review checklist for devop reviews.
cmux-testing
A regression test for a bug fix ships as two commits so CI proves the test catches the bug.
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"…