work-route

work-route is a skill for Claude Code from YuDefine/nuxt-supabase-starter. It costs 44 tokens per session (759 once invoked), scanned A, original, MIT.

A single entry point for starting or continuing software work. It identifies the relevant task, loads the responsible workflow, checks prerequisites, performs authorised steps, and continues through acceptance and delivery.

In plain words
What is it for?
Use it to begin a project, resume existing work, handle changes or hotfixes, and route reproducible regressions through the appropriate process.
Why use it?
It removes the need to choose and invoke separate workflow commands yourself. It also prevents work from skipping required checks or acceptance steps.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: reads .claude/ paths; mentions Codex.

Good fit Use it to begin a project, resume existing work, handle changes or hotfixes, and route reproducible regressions through the appropriate process.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/yudefine/nuxt-supabase-starter/work-route
Install

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.

Any agent
npx skills add YuDefine/nuxt-supabase-starter --skill work-route
Clone the repo
git clone --depth 1 https://github.com/YuDefine/nuxt-supabase-starter

Made for: Claude Code.

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.

agentmods badge for work-route

README.md
[![agentmods](https://agentmods.dev/badge/skills/yudefine/nuxt-supabase-starter/work-route/github.svg)](https://agentmods.dev/skills/yudefine/nuxt-supabase-starter/work-route)
Your own site
<a href="https://agentmods.dev/skills/yudefine/nuxt-supabase-starter/work-route"><img src="https://agentmods.dev/badge/skills/yudefine/nuxt-supabase-starter/work-route/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.

agentmods 80×15 button for work-route

Your own site · 80×15
<a href="https://agentmods.dev/skills/yudefine/nuxt-supabase-starter/work-route"><img src="https://agentmods.dev/badge/skills/yudefine/nuxt-supabase-starter/work-route.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 759 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00044 $0.00759
Opus 5.5 $0.00018 $0.00304
Sonnet 5.5 $0.00009 $0.00152
Haiku 4.5 $0.00004 $0.00076

Measured 8d ago against content hash e7bc8a1822a6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

work-route 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 8d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (rules/.workflow/gherkin-and-dsl/scripts/audit_feature_dsl_topology.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

template/.claude/skills/work-route/SKILL.md · 26 lines

What it actually says

work-route(統一工作入口)

使用者描述想完成的工作即可。本 skill 持有從需求到驗收、交付的接續責任:定位同一工作、載入正確 owner 的契約、執行已授權步驟、處理可修復前提,再依結果繼續;不是只列出「下一支 skill」的導航頁,也不由 router 冒充 owner 或跳過驗收。

每一步只讀該步命中的判準檔(路徑相對本 skill 根:Claude .claude/skills/work-route/、Codex .agents/skills/work-route/),NEVER 一次讀完全部 rules/。

  • 入口. READ 若收到需求(新工作、bug、重構、續跑、狀態查詢),讀取 rules/需求分流與免package.md,取處理列與 work_kind。
  • 第 0 步. READ 若接下來會寫任何檔(含 constitution 修補、免 package、調查證據、package 骨架),讀取 rules/worktree隔離與work-id.md,先過 worktree isolation gate。
  • 第 1 步. READ 若要續跑既有工作、提出方案或鑄新 work id,讀取 rules/定位既有工作與鑄id.md。READ 若要開 package 或改判工作種類,讀取 rules/工作種類與必要產物.md。
  • 第 2 步. READ 若要載入任何下游 owner,每一次先讀取 rules/上游覆寫-lifecycle落點與doctor.md,再讀取 rules/owner載入與代打.md(owner 位置表、explicit 入口代打、clade overlay、SpecFormula 契約)。READ 若要交棒給 owner,讀取 owner-routing.md 決定執行者。
  • 第 3 步. READ 若 owner 的輸入前提缺失,或 vp check/typecheck/lint/測試失敗,讀取 rules/前提修復與gate失敗.md。
  • 第 4 步. READ 若要判定 package 的下一步,讀取 rules/依產物推進.md,處理第一個未完成項目(先過第 2–3 步),做完回本步。
  • 第 5 步. READ 若 tasks 全部完成、要驗收、開 PR、交付或回報,讀取 rules/驗收交付與回報.md。

預設持續推進到使用者要求的成果完成,或到必要的人類決策/不可自行解除的外部阻塞。

Files

What ships with it

60 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.

Changes

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.

  1. 8d ago Changed · -240 lines e7bc8a1822a6
  2. 9d ago Changed · +38 lines b0e58cfeb2f9
  3. 15d ago Changed · +3 lines ccb1ac345ff6
  4. 16d ago Changed · +13 lines 1b043a29190b
  5. 17d ago Changed · +3 lines 984d60074ce9
  6. 19d ago Changed · +23 lines · +11 tokens per session 359bf618a7ad
  7. 21d ago Changed · +14 lines 4d255d05329c
  8. 23d ago Changed · +2 lines d5f9747aaaea
  9. 24d ago First seen · 170 lines · 33 tokens per session scan A 4dd45d9186d7

Subscribe to this mod's changes

work-route is a skill published in the GitHub repository YuDefine/nuxt-supabase-starter (44 stars, last pushed 2d ago), licensed MIT. It adds 44 tokens to every session and 759 once invoked, about $0.0002 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-09-23.

Related

Other skills, from other repositories

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…

HugoRCD/evlog · 89 tokens

product

Consolidated Galyarder Framework Product intelligence bundle.

skillmds/skillmd · 13 tokens

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.

nWave-ai/nWave · 39 tokens

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.

nWave-ai/nWave · 48 tokens

issue-tracker-ingestion

Pull issue/PR/ticket details from Jira, GitHub Issues, Linear, or Azure Boards via MCP into 01-spec.md ## Source. Use at the start of /spec whenever the user references an external ticket.

loiane/specs-driven-development-spring-angular · 53 tokens

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"…

mattgierhart/PRD-driven-context-engineering · 125 tokens