菜单
Use when changing config/models.jsonc — tier policy, role assignments, provider routing, cost/quota visibility. Do not use for target registry or overlay changes.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | control-plane-model-registry |
| version | 2026-04-10.1 |
| description | Use when changing config/models.jsonc — tier policy, role assignments, provider routing, cost/quota visibility. Do not use for target registry or overlay changes. |
| user-invocable | true |
config/models.jsonccapability_tier, cost_tier, billing_mode, or default_rolesprovider_order priorities or marking routes disfavoredquota_visibility, concurrency, or latency_tierconfig/models.jsonc is the single source of truth for model metadata.src/model-registry.ts owns the schema — never add fields to the jsonc that the schema does not validate.src/cli/model-commands.ts renders the registry — update render logic when fields are added.src/model-registry.test.ts — run them before committing.config/models.jsonc and src/model-registry.ts (schema + validators).npm test — confirm model registry tests pass.bin/aicoder-opencode list-models — confirm the change appears correctly.| File | Role |
|---|---|
config/models.jsonc | Canonical model registry — edit here |
src/model-registry.ts | Schema, validators, loaders |
src/cli/model-commands.ts | Render + interactive editor |
src/model-registry.test.ts | Registry unit tests |
config/models.jsonc without running testsdefault_rolesquota_visibility: hidden for models used as defaultsopencode modelsUse when asked to work in a continuous loop until done or truly blocked. Orchestrates pickup, planning, TDD execution, implementation waves when needed, debugging side-chains, verification, and resume behavior.
Use before planning when a feature or change request is underspecified. Resolve high-impact ambiguity around scope, consumers, security, failure handling, and acceptance criteria before writing the implementation plan.
Use for both preparing work for review and responding to review feedback. Keep review evidence local, concrete, and scoped to the real contract. Verify technically before agreeing or changing code.
Use before implementation. Merge design discovery and plan writing into one DR-specific flow: identify the consumer, inspect the repo, debate boundaries with partner and combatant, and produce an execution-ready plan that hands off cleanly into DR-native tasks, TDD, and implementation waves.
Use for the last mile: rerun verification, inspect diffs, commit or push if requested, and perform local docker-compose checks when needed. This is the DR local-tools replacement for MCP-style finish/deploy carryovers.
Use after planning and before implementation when you need a concrete, dependency-ordered task list. Turn the DR feature spec and plan into independently testable task slices with exact file paths and verification commands.