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 api-plangit 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/api-plan)<a href="https://agentmods.dev/skills/yudefine/nuxt-supabase-starter/api-plan"><img src="https://agentmods.dev/badge/skills/yudefine/nuxt-supabase-starter/api-plan/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/api-plan"><img src="https://agentmods.dev/badge/skills/yudefine/nuxt-supabase-starter/api-plan.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.00069 | $0.00736 |
| Opus 5 | $0.00034 | $0.00368 |
| Sonnet 5 | $0.00014 | $0.00147 |
| Haiku 4.5 | $0.00007 | $0.00074 |
Grade A, and why
api-plan 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.
What it actually says
API Plan
api-plan 是 specs/truth/contracts/** 的 truth owner。它不再產出 package-local contract，而是直接維護整個系統目前唯一 API truth。
SOP
Phase 1 -- 對齊 API truth 與 plan handoff
- READ 讀取使用者需求、呼叫者 handoff、plan package 的
spec.md、research.md、plan.md、truth-delta.md、specs/truth/techstack.md、既有specs/truth/contracts/**與指定後端 / API 介面名稱。 - READ 讀取
templates/openapi.yaml與templates/openapi.example.yaml，確認 contract artifact 的固定結構與完成樣貌。 - READ 讀取
.agents/constitution/CONSTITUTION.md、.agents/constitution/shared.md與.agents/constitution/skills/api-plan/openapi.md。
Phase 2 -- 盤點 API ADD / MODIFY / DELETE
- THINK 依需求、handoff、現有 OpenAPI 與 truth-delta，整理本輪要新增、修改、刪除或保持不變的 operation、schema、field、response、error code 與狀態轉移語意。
- DELEGATE 若高影響 MODIFY / DELETE 會改變既有對外契約、請求/回應形狀、錯誤模型或狀態轉移，且尚未有明確使用者決策，呼叫
/clarify；未收斂前停止。
Phase 3 -- 更新 API truth
- WRITE 直接更新
specs/truth/contracts/**，使 API truth 成為目前完整系統契約，不留下「仍以某 plan 契約為準」的分散引用。 - READ 回頭檢查 contract 是否符合已載入憲法、指定介面需求與既有 truth 的相容性；若不符合，立即修正。
- THINK 將 API truth 改動整理為語意單元層級的 ADD / MODIFY / DELETE / NOOP 列。
Phase 4 -- 更新 truth-delta 並交付
- DELEGATE 呼叫
/truth-delta，傳入 plan package、truth root、owner/api-plan與本輪 API truth 改動列。 - WRITE 向使用者回報更新的 API truth 路徑、主要操作與 schema 變更、是否進入
/clarify、truth-delta 更新結果，以及是否可交給後續實作或/tasks。
What ships with it
2 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 · -1 lines af11510f8821
- yesterday First seen · 42 lines · 69 tokens per session scan A 45b40041bbe8
api-plan is a skill published in the GitHub repository YuDefine/nuxt-supabase-starter (45 stars, last pushed today), licensed MIT. It adds 69 tokens to every session and 736 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-10.
Other skills, from other repositories
supabase
Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions, JWT, cookies…
nw-fp-hexagonal-architecture
Hexagonal architecture patterns with pure core and side-effect shell for functional codebases.
django-tdd
Django testing strategies with pytest-django, TDD methodology, factoryboy, mocking, coverage, and testing Django REST Framework APIs.
nw-legacy-refactoring-ddd
DDD-guided legacy refactoring patterns -- strangler fig, bubble context, ACL migration, 14 tactical/strategic/infrastructure patterns, and incremental monolith-to-microservices methodology.
nw-ddd-tactical
Tactical DDD — aggregate design rules, entities, value objects, domain events, repositories, domain services, and anti-pattern detection.
springboot-tdd
Test-driven development for Spring Boot using JUnit 5, Mockito, MockMvc, Testcontainers, and JaCoCo. Use when adding features, fixing bugs, or refactoring.