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 constitutiongit 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/constitution)<a href="https://agentmods.dev/skills/yudefine/nuxt-supabase-starter/constitution"><img src="https://agentmods.dev/badge/skills/yudefine/nuxt-supabase-starter/constitution/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/constitution"><img src="https://agentmods.dev/badge/skills/yudefine/nuxt-supabase-starter/constitution.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.00094 | $0.01112 |
| Opus 5 | $0.00047 | $0.00556 |
| Sonnet 5 | $0.00019 | $0.00222 |
| Haiku 4.5 | $0.00009 | $0.00111 |
Grade A, and why
constitution 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
Constitution
將使用者對 artifact 規範的需求轉成 .agents/constitution/ 下的最小憲法變更。優先重用
既有 CONSTITUTION.md、shared.md 與 skills/<skill>/<artifact>.md；只有在需求真的
新增治理邊界或新增 artifact 時才建立新檔。若缺口會改變規則落點、適用範圍或規則強度，
先訪談使用者，不自行補完。
SOP
Phase 1 -- 定位本次要改的憲法檔
- READ 讀取使用者需求與
.agents/constitution/現況，確認本次是新增、修改或拆分規則，並收斂候選目標檔為CONSTITUTION.md、shared.md或skills/<skill>/<artifact>.md。 - READ 若需要判斷規則應落在 shared、根憲法或某個 skill artifact，讀取
rules/目標檔定位與規則落點判準.md，再依已載入規則收斂本次最小修改面。 - THINK 列出本次真正需要新增或修改的檔案；若某條需求不影響現有憲法結構，避免擴張到其他檔案。
Phase 2 -- 收斂高影響缺口並訪談使用者
- THINK 先從需求中判斷是否存在會改變規則落點、適用 skill、適用 artifact、規則強度或是否需要新檔的高影響缺口。
- READ 若需要判斷哪些缺口必須先問，讀取
rules/高影響缺口與最小訪談判準.md，再依其要求收斂本輪 1 至 3 題。 - DELEGATE 若仍有高影響缺口，呼叫
/clarify，指定提問面向為規則落點、適用 artifact、硬性程度與是否增量修改；未收斂前停止，不自行假設答案。
Phase 3 -- 撰寫最小憲法增量
- THINK 依已確認需求決定本次應修改
CONSTITUTION.md、shared.md或單一skills/<skill>/<artifact>.md；若新增 skill artifact 規則檔，沿用既有檔名慣例與 RuleFile 結構。 - READ 若需要控制改動範圍與避免過度撰寫，讀取
rules/最小增量與必要覆寫判準.md，再依其要求只保留支撐本次需求的最小規則集合。 - WRITE 更新目標憲法檔；若新增或修改 artifact 規則，沿用
Applies To、## Rule N - ...、- Level:、### Good Example、### Bad Example的既有格式。 - READ 回頭檢查是否只動到必要檔案、是否沒有把流程責任寫進 artifact 憲法，以及 shared / skill 落點是否一致；若不符合，立即修正。
Phase 4 -- 交付與後續 handoff
- WRITE 向使用者回報本次新增或修改的憲法檔、每個檔新增或調整的規則、是否進行
/clarify，以及哪些需求被刻意 defer 到未來 skill 或 artifact。 - WRITE 若後續還需要把某個 skill 接上憲法讀取流程，明示應由
/skill-engineering或對應 skill 編修接續，不在本 skill 內自動擴張實作。
Additional Resources
- 規則落點判準：
rules/目標檔定位與規則落點判準.md - 最小訪談判準：
rules/高影響缺口與最小訪談判準.md - 最小增量判準：
rules/最小增量與必要覆寫判準.md
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.
- today Changed · -1 lines cb2cd84606f0
- yesterday First seen · 53 lines · 94 tokens per session scan A 038a52d69ce9
constitution is a skill published in the GitHub repository YuDefine/nuxt-supabase-starter (45 stars, last pushed today), licensed MIT. It adds 94 tokens to every session and 1,112 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
prd-v07-implementation-loop
Execute implementation within EPICs following test-first development, continuous SoT updates, and code traceability during PRD v0.7 Build Execution. Triggers on requests to start building, implement an epic, begin coding, or when user asks "start building", "implement epic", "coding", "development", "build execution"…
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"…
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
prd-v04-user-journey-mapping
Map user missions from trigger to value moment, organizing features into coherent paths during PRD v0.4 User Journeys. Triggers on requests to map user journeys, define user flows, describe how users accomplish goals, or when user asks "map user journeys", "define user flows", "user missions", "how do users accomplish…
atomic-tdd
Test-first discipline. Auto-triggers on "let's implement X", "add feature Y", "fix bug Z", "write a test for", "implement", "build out", and similar pre-code-change phrases. Iron rule: failing test exists before production code. Skip only for pure docs/config changes with an explicit "skipped because:" note. Explicit…
use-tdd
Implement a requested increment with red-green-refactor. Use when the user types /use-tdd.