القائمة
Shared maintenance topology and policy for aicoder-opencode — one server per repo, shared plugins, overlay-first changes
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | control-plane-maintenance-base |
| description | Shared maintenance topology and policy for aicoder-opencode — one server per repo, shared plugins, overlay-first changes |
| user-invocable | false |
| models | ["ollama-cloud/kimi-k2-thinking","ollama-cloud/glm-5.1","ollama-cloud/minimax-m2.7"] |
| routing_role | architect |
| routing_complexity | large |
Shared maintenance/control-plane base for repos that attach to the aicoder-opencode
server.
Use this skill when work is about:
aicoder-opencode.aicoder-opencode owns shared maintenance plugins and skills.aicoder-opencode on 8080dr-repo on 8082letta-workspace on 8084src/plugins/.agents/skills/Use config/models.jsonc as the authoritative allowlist. Only models listed there are approved. Provider priority within each registry entry follows provider_order[].priority.
Key providers in the registry:
| Provider | Status | Notes |
|---|---|---|
ollama-cloud/* | Free (rate-capped daily) | Best when cap not exhausted |
iflowcn/* | Free | Major free provider; priority 1 for many registry entries |
mistral/* | Subscription | codestral, devstral variants |
minimax/* | Subscription (minimax.io) | Reliable fallback |
kimi-for-coding/* | Subscription | User-Agent gated, works via opencode |
xiaomi-token-plan-ams/* | Subscription (direct) | mimo-v2-pro priority 1 via token-plan-ams.xiaomimimo.com |
openrouter/:free | Free tier | Allowed; use curated models only |
openrouter/* (paid) | Pay-per-token | Last resort; only models in registry |
longcat-openai/* | Free | Special use only — not general fallback |
Never use: xai/grok-*, openai/* (ChatGPT), togetherai/*, uncurated openrouter auto-selection.
| Task type | Primary | Fallback |
|---|---|---|
| Autonomous coding iteration (dr-repo) | ollama-cloud/qwen3-coder:480b | xiaomi-token-plan-ams/mimo-v2-pro |
| Maintenance / type fixes (letta-workspace) | ollama-cloud/devstral-2:123b | xiaomi-token-plan-ams/mimo-v2-pro |
| Fast general iteration | ollama-cloud/kimi-k2.5 | xiaomi-token-plan-ams/mimo-v2-pro |
| Architecture / heavy reasoning | ollama-cloud/kimi-k2-thinking | xiaomi-token-plan-ams/mimo-v2-pro |
Model selection is handled by OpenCode plus the model-registry plugin. The plugin can reroute task launches when the requested provider is in quota backoff, when an agent exposes ordered models: metadata, or when the task falls back to curated registry routing. Do not override model choice with env vars.
The model-registry plugin exposes two tools:
list_curated_models — all registry entries; use freeOnly: true to scope to free providersselect_models_for_role — models recommended for a named role (e.g. "autonomous-agent", "code-review")get_quota_backoff_status — providers currently in quota backoff and when they expireRules:
get_quota_backoff_status. If a needed provider is in backoff, let the plugin reroute task launches using the current agent models: list or the curated registry fallback.longcat, claude, gpt, or grok models automatically. These are subscription-gated or architecturally undesirable as automatic fallbacks.model-registry plugin based on the model's capability_tier. Do not override temperature in prompts.These rules apply to all repo maintenance sessions (dr-repo autopilot, letta-workspace maintenance, aicoder unblock-and-patch):
When the autopilot timer fires:
--session <id>.get_quota_backoff_status before starting a long chain — if the configured model's provider is in backoff, switch to the next provider in the priority table above.The plugin tracks quota events automatically and backs off providers for 1 hour on HTTP 429 or quota-keyword errors. No manual action is needed during normal operation.
If you observe a provider persistently failing (beyond the 1-hour window), call get_quota_backoff_status and route around it using the curated fallback in provider_order.
Downstream skills and agents that consume this base inherit the following verification rules:
VERDICT: PASS, VERDICT: FAIL, or VERDICT: PARTIAL. Plain text, no markdown, no hedging.See targets/dr-repo/overlay/.opencode/agents/verifier.md for the full probe checklist and output block format.
aicoder-opencodeUse 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.