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 agentmods add commands/yudefine/nuxt-supabase-starter/validate-startergit 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/commands/yudefine/nuxt-supabase-starter/validate-starter)<a href="https://agentmods.dev/commands/yudefine/nuxt-supabase-starter/validate-starter"><img src="https://agentmods.dev/badge/commands/yudefine/nuxt-supabase-starter/validate-starter.svg" alt="Measured on agentmods" 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.00029 | $0.00853 |
| Opus 5 | $0.00015 | $0.00426 |
| Sonnet 5 | $0.00006 | $0.00171 |
| Haiku 4.5 | $0.00003 | $0.00085 |
Grade C, and why
Validate Starter scanned grade C with 1 finding 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 5d ago.
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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf template/temp/validate-starter How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validate Starter Template
此 command 屬 root meta 維護層,只給 starter 維護者使用。scaffold 出去的使用者專案不會拿到它
(見 .claude/rules/starter-hygiene.md § L3 Commands Hygiene)。
驗證對象是本 repo 的 template/ starter seed,而不是當前 repo root。
Instructions
Phase 1: 結構與文件基線(root script)
bash scripts/validate-starter.sh # auto 偵測 demo / clean 模式
bash scripts/validate-starter.sh clean # 指定驗證 clean 模式
bash scripts/validate-starter.sh demo # 指定驗證 demo 模式
該 script 以 template/ 為 root,涵蓋:
- Phase 1 結構檢查(
.claude/、openspec/、app/、server/、docs/decisions/) - Phase 2
package.jsonscripts 完備性 - Phase 3 文件關鍵字一致性
- Phase 3b Spectra / OpenSpec clean baseline
- Phase 4 mode-specific 檢查
在開發中的 repo 跑會在 Phase 3b 出現 FAIL(active change dir 尚未 archive),那是預期的; clean baseline 只對 scaffold 輸出或 release 前的乾淨樹有意義。
Phase 2: Scaffold 模擬(preset 全覆蓋)
cd template && vp run validate:starter
template/scripts/validate-starter.mjs 會對每個 preset(baseline / d-pattern-audit /
nuxthub-ai / none)跑 scaffold simulation,把輸出落在 template/temp/validate-starter/,
並驗證 strip manifest 與 audit signal。
Phase 3: Public hygiene
node scripts/audit-template-hygiene.sh # starter pollution 檢查
node scripts/audit-public-hygiene.mjs # L3 commands / skills allowlist 檢查
Phase 4: 手動一致性抽查
比對 template/docs/QUICK_START.md、template/README.md、template/docs/CLAUDE_CODE_GUIDE.md
內描述的目錄樹與實際結構:
grep -n "├──\|└──" template/docs/QUICK_START.md template/docs/CLAUDE_CODE_GUIDE.md template/README.md
Phase 5: Tech Stack 對照
從 template/README.md 的 Tech Stack 章節解析 [Name](url) 連結,與 template/package.json
的 dependencies 比對,確認 README 宣稱的技術都實際安裝。
Output
輸出驗證報告:
## Starter Validation Report
**來源 Commit**: <git rev-parse --short HEAD>
| 階段 | 狀態 | 備註 |
| --------------------------- | ----- | ---- |
| validate-starter.sh | ✅/❌ | |
| validate:starter (scaffold) | ✅/❌ | |
| audit-template-hygiene | ✅/❌ | |
| audit-public-hygiene | ✅/❌ | |
| 文件一致性 | ✅/❌ | |
| Tech Stack | ✅/❌ | |
## 總結: **PASS** / **FAIL**
### 發現的問題(如有)
1. ...
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.
- 5d ago First seen · 95 lines · 29 tokens per session scan C 74cd3bde2e88
Validate Starter is a command published in the GitHub repository YuDefine/nuxt-supabase-starter (45 stars, last pushed today), licensed MIT. It adds 29 tokens to every session and 853 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
tdd-requirements
TDD開発の要件整理を行います。機能要件を明確化し、テスト駆動開発のための準備を行います。.
dashboard
Generar dashboard HTML local con métricas de eficiencia del proyecto SDD.
web-build-fix
Diagnose and resolve web build, bundling, or deployment issues.
speckit.tdd.plan
Derive the feature's test list by delegating to zfa tdd plan (deterministic engine); falls back to LLM-guided derivation only when zfa is unavailable.
p5-impl-green
Writes the minimal production code that makes the existing tests green. No over-engineering.
tdd
Test-driven development with TodoWrite planning and comprehensive testing.