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 subagent-devgit 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/subagent-dev)<a href="https://agentmods.dev/skills/yudefine/nuxt-supabase-starter/subagent-dev"><img src="https://agentmods.dev/badge/skills/yudefine/nuxt-supabase-starter/subagent-dev/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/subagent-dev"><img src="https://agentmods.dev/badge/skills/yudefine/nuxt-supabase-starter/subagent-dev.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 116 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- high Excessive Agency · line 131 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
- high Excessive Agency · line 131 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00070 | $0.03346 |
| Opus 5 | $0.00035 | $0.01673 |
| Sonnet 5 | $0.00014 | $0.00669 |
| Haiku 4.5 | $0.00007 | $0.00335 |
Grade A, and why
subagent-dev 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Subagent-Driven Development
Execute plan by dispatching a fresh implementer subagent per task, a task review (spec compliance + code quality, one reviewer, two verdicts) after each, and a broad whole-branch review at the end.
Why subagents: You delegate tasks to specialized agents with isolated context. By precisely crafting their instructions and context, you ensure they stay focused and succeed at their task. They should never inherit your session's context or history — you construct exactly what they need. This also preserves your own context for coordination work.
Core principle: Fresh subagent per task + task review (spec + quality) + broad final review = high quality, fast iteration
Routing gate: 先看 [[agent-routing]] — Routing Table / Orchestration Residency 命中 pi 路徑（mechanical sweep、Codex-primary 工作、非 view phase 的實作）時優先走該表；本 skill 用於 Claude-primary 場景的 plan 執行。回報契約遵循 [[agent-routing]] § Subagent 回報契約。
Narration: between tool calls, narrate at most one short line — the ledger and the tool results carry the record.
Continuous execution: Do not pause to check in with 使用者 between tasks. Execute all tasks without stopping. The only reasons to stop: BLOCKED you cannot resolve, ambiguity that genuinely prevents progress, or all tasks complete.
When to Use
- Have an implementation plan（
/tasks產出的specs/plans/NNN-<slug>/tasks.md、docs/phases/、或 manual plan）？ - Tasks mostly independent？
- Claude-primary（非 pi 路徑）且要留在當前 session？
三者皆是 → 用本 skill。Tasks tightly coupled → 主線自己做或先拆 plan。
The Process
Setup
- Read plan once；note global constraints（plan 的 Global Constraints 段或 spec 的專案級要求）
TaskCreate每個 task- Check ledger：
cat "$(git rev-parse --show-toplevel)/.clade/sdd/progress.md"（存在 → 從第一個未標 complete 的 task 續跑，不重派已完成的） - 記錄目前 commit 當第一個 task 的 BASE
Pre-Flight Plan Review
Dispatch Task 1 前掃一次 plan：task 間互相矛盾、task 與 Global Constraints 矛盾、plan 明文要求但 review rubric 視為 defect 的東西（不 assert 的 test、大段 verbatim duplication）。發現 → 一次打包問 使用者（每條 finding 附 plan 原文，問哪個作準），不要執行中一條一條打斷。乾淨 → 直接開始。
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.
- today Changed 0b1b9e4ff2ba
- 2d ago Changed · -2 lines c3d75a16c90d
- 3d ago Changed ed2594c52733
- 6d ago First seen · 172 lines · 70 tokens per session scan A e8b839910705
subagent-dev is a skill published in the GitHub repository YuDefine/nuxt-supabase-starter (45 stars, last pushed today), licensed MIT. It adds 70 tokens to every session and 3,346 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
self-review
Weekly pass over the evlog repository and Evi's own surface, in two halves — what has drifted out of coherence (a capability wired but never consumed, code contradicting a written guide, a description promising a tool the allowlist lacks), and what is missing (a capability worth having, a manual step worth automating…
nw-fp-usable-design
Naming conventions, API ergonomics, and usability patterns for functional code.
nw-review
Dispatches an expert reviewer agent to critique workflow artifacts. Use when a roadmap, implementation, or step needs quality review before proceeding.
software-code-refactoring
Improve production code quality while preserving all existing test behavior. Commonly used for the Refactor phase of TDD red-green-refactor, but applicable to any codebase with tests. Use when production code works but needs cleanup — reducing duplication, improving naming, simplifying complexity, aligning with…
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"…
code-review
Independent review feedback orchestrator -- Reads upstream superpowers:receiving-code-review as baseline, layers personal rules (grilling clarification / tdd delegation). Optionally invokes cli-code-review to dispatch reviews.