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 system-analysisgit 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/system-analysis)<a href="https://agentmods.dev/skills/yudefine/nuxt-supabase-starter/system-analysis"><img src="https://agentmods.dev/badge/skills/yudefine/nuxt-supabase-starter/system-analysis/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/system-analysis"><img src="https://agentmods.dev/badge/skills/yudefine/nuxt-supabase-starter/system-analysis.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.00093 | $0.00907 |
| Opus 5 | $0.00046 | $0.00453 |
| Sonnet 5 | $0.00019 | $0.00181 |
| Haiku 4.5 | $0.00009 | $0.00091 |
Grade A, and why
system-analysis 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.
What it actually says
System Analysis
system-analysis 是 planner orchestration skill。它本身不修改 truth，但必須把本輪 plan 與既有 truth 的差異帶給後續 owner，避免 API、data、UI 分析各自推理不同版本。
SOP
Phase 1 -- 對齊 plan、truth 與控制平面
- READ 讀取使用者需求、呼叫者要求、目標 plan package 的
spec.md、research.md、truth-delta.md、既有plan.md、specs/truth/techstack.md與相關specs/truth/**。 - READ 讀取
templates/plan.md與templates/plan.example.md，確認plan.md的固定結構與完成樣貌。 - READ 讀取
.agents/constitution/CONSTITUTION.md、.agents/constitution/shared.md與.agents/constitution/skills/system-analysis/plan.md。 - WRITE 若 plan package 尚未有
plan.md父層，建立必要目錄；本 skill 不建立或修改specs/truth/**。
Phase 2 -- 收斂系統介面盤點與 clarify 策略
- THINK 從需求原文、
spec.md、research.md、truth-delta.md與現有 truth 整理本次需求部位、外部依賴、資料責任、UI 責任與技術端點。 - READ 需要判斷介面邊界時，讀取
rules/系統介面盤點與端點歸類判準.md。 - DELEGATE 若缺口會改變系統介面數量、端點類型、介面邊界、truth owner 責任或 Wave 切分，呼叫
/clarify；未收斂前停止。
Phase 3 -- 規劃分析 Wave 並產出 plan
- READ 需要判斷先後與平行分組時，讀取
rules/Wave依賴排序與平行分組判準.md。 - THINK 依介面依賴、truth 變更風險與可平行程度安排 Wave，確認每個介面至少被一個後續 planner 承接。
- WRITE 將系統介面盤點、Wave、分析重點與委派理由寫入
specs/plans/NNN-<slug>/plan.md。
Phase 4 -- 委派 planner 並交付
- READ 需要判斷 planner 對應時，讀取
rules/分析介面委派與planner對應判準.md。 - DELEGATE 依 Wave 順序將 API 介面交給
/api-plan、資料介面交給/data-plan、UI 介面交給/ui-plan；每次 handoff 都必須包含 plan package path、truth root、truth-delta path、介面名稱與分析重點。 - WRITE 向使用者回報
plan.md、系統介面數量、Wave 數量、委派到哪些 planner，以及是否可進入/dsl-refine或/tasks。
What ships with it
5 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 · -1 lines scan C → A 6f1a17371104
- 2d ago First seen · 45 lines · 93 tokens per session scan C 57221f975ee5
system-analysis is a skill published in the GitHub repository YuDefine/nuxt-supabase-starter (45 stars, last pushed today), licensed MIT. It adds 93 tokens to every session and 907 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
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"…