opencode-model-variant-management

Add new models, providers, or variants to OpenCode configurations with validation.

6|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/open-hax/opencode-skills --skill opencode-model-variant-management
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opencode-model-variant-management
Source: https://github.com/open-hax/opencode-skills/tree/main/.opencode/skills/opencode-model-variant-management
Command: npx skills add https://github.com/open-hax/opencode-skills --skill opencode-model-variant-management

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenCode teams need a reliable way to add new models, providers, or model variants with correct configuration, authentication, and validation to avoid misconfigurations and integration failures.

Core Features & Use Cases

  • Update provider configurations and validation rules to support new models and variants.
  • Add or adjust model variants, routing rules, and authentication flows across providers.
  • Verify auth, rate limits, and fallback behavior; keep documentation and examples in sync.

Quick Start

Provide a new model/provider variant by updating OpenCode configuration and validation rules, then run the validation workflow.

Frequently Asked Questions about opencode-model-variant-management

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new model variant to OpenCode provider configurations?

To add a new model variant to OpenCode provider configurations, you update the provider configuration files and validation rules. This ensures correct routing and authentication flows across the integrated providers.

What is the process for validating credentials when integrating a new provider?

Validating credentials for a new provider integration involves running the OpenCode validation workflow. This verifies authentication, rate limits, and fallback behavior to prevent misconfigurations and integration failures.

Can I adjust routing rules and fallback behaviors across multiple providers?

Yes, you can adjust routing rules and fallback behaviors across multiple providers. The workflow allows you to add or modify provider variants while ensuring proper authentication and validation are applied.

How do I keep documentation in sync when updating provider configurations?

Keeping documentation in sync when updating provider configurations is handled within the variant management workflow. It ensures examples and validation rules are updated alongside the new model or provider integration.

Why does my model variant configuration fail validation?

Model variant configuration validation fails when authentication credentials, routing rules, or provider settings are incorrect. Running the OpenCode validation workflow identifies these issues to prevent integration failures.

What's the best way to manage model variants without breaking existing auth flows?

The best way to manage model variants without breaking existing auth flows is to use a structured configuration and validation workflow. This verifies credentials and updates routing rules safely across providers.