Borrowing it
Nothing to install: this file belongs to c9r-io/orchestrator. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/c9r-io/orchestrator/main/.claude/skills/design-governance/SKILL.mdgit clone --depth 1 https://github.com/c9r-io/orchestratorWrote 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/c9r-io/orchestrator/design-governance)<a href="https://agentmods.dev/skills/c9r-io/orchestrator/design-governance"><img src="https://agentmods.dev/badge/skills/c9r-io/orchestrator/design-governance/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/c9r-io/orchestrator/design-governance"><img src="https://agentmods.dev/badge/skills/c9r-io/orchestrator/design-governance.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.00101 | $0.02084 |
| Opus 5 | $0.00051 | $0.01042 |
| Sonnet 5 | $0.00020 | $0.00417 |
| Haiku 4.5 | $0.00010 | $0.00208 |
Grade A, and why
design-governance 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 12d 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.
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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Governance Workflow
Govern a Design Brief from draft through implementation to visual validation and closure. This is the design-first counterpart to fr-governance — where FR governance drives functional implementation, design governance drives user experience implementation.
When to Use
- A Design Brief exists under
docs/design_brief/and needs to be implemented - The user wants to validate that a UI implementation matches its design intent
- The user says "治理设计" or asks to govern/close a design brief
Phase 1: Select Design Brief
- Scan
docs/design_brief/recursively for*.mdfiles (excludeREADME.md) - If no brief files found, inform the user and stop
- If exactly one brief, auto-select and confirm with user
- If multiple briefs, present a numbered list with title, module, status, and target, then ask which one to govern
- Read the selected brief fully to understand screens, flows, components, and constraints
Phase 2: Design Review
Enter plan mode. Audit the brief for completeness and alignment before implementation.
2.1 Completeness Check
Verify the brief covers all required sections:
| Section | Required | Check |
|---|---|---|
| Design Intent (problem, users, success criteria) | Yes | Has concrete problem statement, not just "we need X" |
| Screens (layout, components, interactions, states) | Yes | Every screen has normal + empty + loading + error states |
| User Flows | Yes | At least one happy-path flow documented |
| Design Constraints | Yes | References docs/design-system.md tokens, not hardcoded values |
| Navigation entry points | Yes | Every screen specifies how users reach it |
| Accessibility notes | Recommended | ARIA roles, keyboard nav, contrast |
Flag missing sections and propose additions. The user decides whether to fill gaps now or proceed.
2.2 Design System Alignment
Read docs/design-system.md and cross-check:
- Are referenced tokens valid? (token names exist in the design system)
- Do component variants match what the design system defines?
- Are responsive breakpoints consistent with the system's breakpoint strategy?
- Are accessibility requirements at least as strict as the system baseline?
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.
- 12d ago First seen · 201 lines · 101 tokens per session scan A 233b89234ddc
design-governance is a skill published in the GitHub repository c9r-io/orchestrator (21 stars, last pushed 11d ago), licensed MIT. It adds 101 tokens to every session and 2,084 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-08-30.
Other skills, from other repositories
cw-slice
Use before writing code for any Codewhale feature, upgrade, or refactor: find the existing owner of the behavior, bound the change to one reviewable slice, and fix the evidence bar before you start.
gh-compile-issues
Triage N GitHub issues into a coverage matrix: fetch each, check current code, classify already-done/quick-fix/design/defer with cited evidence.
gh-find-prs
Survey open Codewhale PRs and triage each for mergeability and disposition against the real landing branch.
review
Diff-scoped correctness review that reads the codebase around the change — callers, contracts, and invariants — and returns line-anchored findings ranked by severity with confidence, then a merge-risk verdict. Use for reviewing a PR, diff, or named change set. Not for style review, approvals-as-rubber-stamp, or…
frontend-design
Produce intentional, responsive, accessible UI work and perform visual QA instead of generic component assembly.
simplify
Improve clarity and reduce needless complexity after behavior is understood; preserve behavior and keep cleanup separate from correctness fixes.