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 truth-deltagit 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/truth-delta)<a href="https://agentmods.dev/skills/yudefine/nuxt-supabase-starter/truth-delta"><img src="https://agentmods.dev/badge/skills/yudefine/nuxt-supabase-starter/truth-delta/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/truth-delta"><img src="https://agentmods.dev/badge/skills/yudefine/nuxt-supabase-starter/truth-delta.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.00088 | $0.00846 |
| Opus 5 | $0.00044 | $0.00423 |
| Sonnet 5 | $0.00018 | $0.00169 |
| Haiku 4.5 | $0.00009 | $0.00085 |
Grade A, and why
truth-delta 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
Truth Delta
truth-delta 是 truth owner skill 的共同 handoff skill。它不決定要怎麼改 truth，也不替 owner 寫 OpenAPI、DBML、feature 或 DSL；它只負責把已確認的 truth 變更，以固定格式寫入當前 plan package 的 truth-delta.md，讓下游 skill 能接續推理。
SOP
Phase 1 -- 對齊 plan package 與 truth owner
- READ 讀取呼叫者 handoff、當前 plan package 路徑、truth root、truth owner 名稱、已檢查或已修改的 truth 規格清單，以及既有
truth-delta.md內容。 - READ 讀取
rules/Truth變更分類與粒度判準.md，確認 owner section、動作分類、語意單元粒度與 NOOP 記錄規則。 - READ 若
truth-delta.md尚不存在，讀取templates/truth-delta.md與templates/truth-delta.example.md，確認初始化骨架與完成樣貌。 - WRITE 若
truth-delta.md尚不存在，於當前 plan package 建立該檔案，並填入 plan package、truth root 與四個 truth owner section。
Phase 2 -- 收斂本輪 truth 變更紀錄
- THINK 依已載入規則，把呼叫者提供的 truth 改動整理成語意單元列；每列必須包含
ADD、MODIFY、DELETE或NOOP，以及 truth 規格、改動摘要與原因。 - THINK 若呼叫者宣稱有高影響
MODIFY或DELETE，但 handoff 未說明已完成/clarify或明確風險決策，停止寫入並要求呼叫者先補齊確認依據。 - THINK 若同一 truth owner 本輪沒有 truth 變更，收斂一列
NOOP，明示已檢查但無需變更的 truth 範圍與原因。
Phase 3 -- 更新 owner section
- WRITE 在
truth-delta.md的對應 owner section 追加或更新本輪表格列；若該 section 仍是 placeholder 或既有NOOP已被實際改動取代，先清理再寫入。 - READ 回頭檢查
truth-delta.md是否仍保留每個 truth owner 各一張表，且所有列都符合固定欄位、動作值與語意單元粒度；若不符合，立即修正。
Phase 4 -- 交付下游 handoff
- WRITE 向呼叫者回報已更新的
truth-delta.md路徑、owner section、ADD / MODIFY / DELETE / NOOP 數量，以及是否仍有需回到/clarify的高影響 truth 變更。
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.
- yesterday Changed bbf2fa895e00
- 2d ago First seen · 42 lines · 88 tokens per session scan A 4d586ef094e0
truth-delta is a skill published in the GitHub repository YuDefine/nuxt-supabase-starter (45 stars, last pushed yesterday), licensed MIT. It adds 88 tokens to every session and 846 once invoked, about $0.0004 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"…