
model-researcher
Add new/custom AI models to opencode.json. Use proactively for bleeding-edge releases, non-standard providers, self-hosted models, or custom endpoints. Examples: - user: "Add the new Claude 4.5" → websearch for API specs, add provider entry with baseUrl, verify model ID format - user: "Use my local Ollama instance" → configure custom provider with http://localhost:11434, set model ID format - user: "Configure this OpenAI-compatible proxy" → add provider with custom baseUrl, set apikey env var, verify compatibility - user: "Model X just released, add it" → research provider documentation, find model ID and capabilities, add to config
- Installs
- 116
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/igorwarzocha/opencode-workflows --skill model-researcher- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads model-researcher automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Model Researcher
Add new or custom AI models to opencode.json with verified specifications.
<critical_prohibition>
EXTREMELY STRICT: Banned Legacy Models
The following models MUST NOT be used in any configuration as they are DEPRECATED, REPLACED, or OBSOLETE in the current Q4 2025 market:
- OpenAI: GPT-o series (
o1-mini,o1-preview), GPT-4o, GPT-4 Turbo. - Anthropic: Claude 3.5 series (
sonnet-3.5, etc.), Claude 3 series. - Google: Gemini 1.5 series, Gemini 2 series.
- Meta: Llama 3 series.
The market has moved to GPT-5.2, Claude 4.5, and Gemini 3. Any attempt to configure these models MUST be rejected. </critical_prohibition>
<when_to_use>
- Model is too new for models.dev
- Non-standard or custom provider (self-hosted, proxy, enterprise)
- User heard about a new release and wants to use it immediately
- Model exists but with non-default configuration needs
</when_to_use>
<question_tool>
Batching: Use the question tool for 2+ related questions. Single questions → plain text.
Syntax: header ≤12 chars, label 1-5 words, add "(Recommended)" to default.
When to ask: Vague model reference, multiple providers available, or specs unverified.
Critical: MUST confirm specs with user before applying model configuration.
</question_tool>
<critical_rule>
Verify Before Configure
MUST NOT hallucinate model specifications. Models have precise identifiers, context limits, and API requirements. A wrong value means broken requests or wasted tokens.
Before ANY configuration:
- Confirm the model actually exists
- Find the exact model identifier (API name, not marketing name)
- Get verified context and output token limits
- Identify required provider configuration
</critical_rule>
<workflow>Step 1: Clarify What the User Wants
Ask if unclear:
- "Which provider will you access this through?" (direct API, OpenRouter, Together, self-hosted, etc.)
- "Do you have API access already, or do you need setup help?"
Step 2: Research the Model
Use web search to find authoritative sources:
websearch("${MODEL_NAME} API context limit tokens official documentation")
websearch("${MODEL_NAME} model ID API identifier ${PROVIDER}")
Priority sources (most to least trustworthy):
- Official provider documentation/blog posts
- Provider's API reference or changelog
- Official GitHub repos or release notes
- OpenRouter/Together model pages (they list specs)
- Reputable tech news (for very new announcements)
Red flags - search more if you only find:
- Reddit speculation
- Tweets without official confirmation
- Your own training data (MAY be outdated)
Step 3: Confirm Findings with User
Before touching config, MUST present your research:
I found the following for [MODEL]:
Provider: OpenAI
Model ID: gpt-5.2-2025-12-11
Context limit: 400000 tokens (Direct) | 272000 tokens (OAuth)
Output limit: 128000 tokens
Special options: [e.g., reasoning modes, vision support]
Source: [URL]
Does this match what you expected? Should I add this to your config?
MUST NOT proceed without user confirmation.
Step 4: Apply Configuration
Read the current config first:
read ~/.config/opencode/opencode.json
Then apply using surgical edits. Choose the right pattern:
Pattern A: GPT-5.2 (OpenAI)
OpenAI GPT-5.2 supports specialized reasoning modes via variants (Cycle with ctrl+t). Note that models configured via OAuth plugins (e.g., opencode-openai-codex-auth) often have different enforced limits.
{
"provider": {
"openai": {
"models": {
"gpt-5.2": {
"limit": { "context": 400000, "output": 128000 }, // Use 272000 for OAuth
"variants": {
"pro": {
"reasoningEffort": "xhigh",
"reasoningSummary": "detailed",
},
"thinking": { "reasoningEffort": "high" },
"instant": { "reasoningEffort": "low", "textVerbosity": "low" },
},
},
"gpt-5.2-codex": {
"limit": { "context": 400000, "output": 128000 }, // Use 272000 for OAuth
},
},
},
},
}
Pattern B: Other Labs (DeepSeek, Zhipu, MiniMax, Moonshot)
For labs using OpenAI-compatible or Anthropic-compatible endpoints (Verified Q4 2025):
{
"provider": {
"deepseek": {
"npm": "@ai-sdk/openai-compatible",
"name": "DeepSeek",
"options": { "baseURL": "https://api.deepseek.com" },
"models": {
"deepseek-v3.2": { "limit": { "context": 128000, "output": 32768 } },
},
},
"zhipu": {
"npm": "@ai-sdk/openai-compatible",
"name": "Zhipu AI (ZAI)",
"options": { "baseURL": "https://api.z.ai/api/paas/v4" },
"models": {
"glm-4.7": { "limit": { "context": 200000, "output": 128000 } },
},
},
"minimax": {
"npm": "@ai-sdk/openai-compatible",
"name": "MiniMax",
"options": { "baseURL": "https://api.minimax.chat/v1" },
"models": {
"minimax-m2.1": { "limit": { "context": 204800, "output": 128000 } },
},
},
"moonshot": {
"npm": "@ai-sdk/openai-compatible",
"name": "Moonshot AI (Kimi)",
"options": { "baseURL": "https://api.moonshot.cn/v1" },
"models": {
"kimi-k2-thinking": { "limit": { "context": 256000, "output": 64000 } },
},
},
},
}
Pattern C: Claude 4.5 Opus (Extended Thinking)
For models that need specific options like Anthropic's extended thinking:
{
"provider": {
"anthropic": {
"models": {
"claude-4-5-opus-thinking": {
"id": "claude-4-5-opus-20251124",
"name": "Claude 4.5 Opus (Extended Thinking)",
"options": {
"thinking": {
"type": "enabled",
"budgetTokens": 32000,
},
},
},
},
},
},
}
Step 5: Validate
After editing, remind user to test:
Config updated. To verify it works:
1. Restart OpenCode or run: opencode
2. Run /models and select [model name]
3. Send a test message
If you see errors, check:
- API key is set (run /connect if needed)
- Model ID matches provider's documentation exactly
- Context limits aren't higher than the model actually supports
<research_queries>
| Scenario | Search Query |
|---|---|
| New OpenAI model | "gpt-5.2" site:openai.com OR site:platform.openai.com |
| New Anthropic model | "claude-4.5" site:anthropic.com API |
| New Google model | "gemini 3" site:ai.google.dev context window |
| OpenRouter availability | "${MODEL}" site:openrouter.ai |
| Together AI availability | "${MODEL}" site:together.ai |
| Self-hosted specs | "${MODEL}" context length output tokens huggingface |
</research_queries>
<spec_checklist>
Before configuring, ensure you have:
- Model ID: Exact API identifier (not marketing name)
- Context limit: Maximum input tokens
- Output limit: Maximum output/completion tokens
- Provider: Which service hosts it
- Base URL: For custom providers only
- Special options: Vision, reasoning modes, thinking budgets
- Availability: Is it actually accessible (not waitlist-only)?
</spec_checklist>
<handling_uncertainty>
If you cannot verify specifications:
- Be honest: "I couldn't find official documentation for the exact context limit."
- Provide best guess with source: "Based on [source], it appears to be 128k, but this isn't confirmed."
- Suggest conservative defaults: "I'll configure with 100k context as a safe starting point. You can increase it once you confirm the actual limit."
- Recommend checking: "Try the provider's /models endpoint or documentation for exact specs."
</handling_uncertainty>
References
references/provider-patterns.md- Common provider configuration examples
FAQ
What does the model-researcher skill do?
Add new/custom AI models to opencode.json. Use proactively for bleeding-edge releases, non-standard providers, self-hosted models, or custom endpoints. Examples: - user: "Add the new Claude 4.5" → websearch for API specs, add provider entry with baseUrl, verify model ID format - user: "Use my local Ollama instance" → configure custom provider with http://localhost:11434, set model ID format - user: "Configure this OpenAI-compatible proxy" → add provider with custom baseUrl, set apikey env var, verify compatibility - user: "Model X just released, add it" → research provider documentation, find model ID and capabilities, add to config
How do I install model-researcher?
Run npx skills add https://github.com/igorwarzocha/opencode-workflows --skill model-researcher in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/model-researcher/ (personal) or .claude/skills/model-researcher/ (project).
Which AI agents can use model-researcher?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is model-researcher safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains model-researcher?
It is published by igorwarzocha in igorwarzocha/opencode-workflows. It has 116 recorded installs.
More from igorwarzocha/opencode-workflows
powerpoint
igorwarzocha/opencode-workflows
Handle PowerPoint (.pptx) creation, design, and analysis. Use for pitch decks, status updates, and visual storytelling. Use proactively when precise layout positioning and design principles are needed. Examples: - user: "Create a 10-slide deck for the board meeting" - use design principles + html2pptx - user: "Convert this report into a presentation" - extract text and map to template - user: "Audit this deck for layout issues" - generate thumbnail grid for inspection
word
igorwarzocha/opencode-workflows
Handle Word document (.docx) creation, editing, and analysis with high-fidelity visual review. Use for professional reports, legal documents, and tracked changes. Use proactively when quality and precise formatting are critical. Examples: - user: "Create a professional report in Word" - use python-docx with render loops - user: "Draft a legal contract with redlines" - use ooxml redlining workflow - user: "Extract text from this DOCX while preserving structure" - use pandoc markdown conversion
security-nextjs
igorwarzocha/opencode-workflows
Review Next.js security audit patterns for App Router and Server Actions. Use for auditing NEXTPUBLIC exposure, Server Action auth, and middleware matchers. Use proactively when reviewing Next.js apps. Examples: - user: "Scan Next.js env vars" → find leaked secrets with NEXTPUBLIC prefix - user: "Audit Server Actions" → check for missing auth and input validation - user: "Review Next.js middleware" → verify matcher coverage for protected routes - user: "Check Next.js API routes" → verify auth in app/api and pages/api - user: "Secure Next.js headers" → audit next.config.js for security headers
create-opencode-plugin
igorwarzocha/opencode-workflows
Create OpenCode plugins using the @opencode-ai/plugin SDK. Use for building custom tools, event hooks, auth providers, or tool execution interception. Use proactively when developing new plugins in .opencode/plugin/ or /.config/opencode/plugin/. Examples: - user: "Create a plugin to block dangerous commands" → implement tool execution before hook with blocking logic - user: "Add a custom tool for jira" → design tool schema and implementation using SDK context - user: "Show toast on file edit" → react to file edit events and display status message - user: "Build a custom auth provider" → implement auth flow for new model provider - user: "Intercept git commits" → add hook to validate commit messages before execution
agent-architect
igorwarzocha/opencode-workflows
Create and refine OpenCode agents via guided Q&A. Use proactively for agent creation, performance improvement, or configuration design. Examples: - user: "Create an agent for code reviews" → ask about scope, permissions, tools, model preferences, generate AGENTS.md frontmatter - user: "My agent ignores context" → analyze description clarity, allowed-tools, permissions, suggest improvements - user: "Add a database expert agent" → gather requirements, set convex-database-expert in subagenttype, configure permissions - user: "Make my agent faster" → suggest smaller models, reduce allowed-tools, tighten permissions
opencode-config
igorwarzocha/opencode-workflows
Edit opencode.json, AGENTS.md, and config files. Use proactively for provider setup, permission changes, model config, formatter rules, or environment variables. Examples: - user: "Add Anthropic as a provider" → edit opencode.json providers, add API key baseEnv var, verify with opencode run test - user: "Restrict this agent's permissions" → add permission block to agent config, set deny/allow for tools/fileAccess - user: "Set GPT-5 as default model" → edit global or agent-level model preference, verify model name format - user: "Disable gofmt formatter" → edit formatters section, set languages.gofmt.enabled = false
Popular backend & apis skills
find-skills
vercel-labs/skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
entra-app-registration
microsoft/azure-skills
Guides Microsoft Entra ID app registration, OAuth 2.0 authentication, and MSAL integration. USE FOR: create app registration, register Azure AD app, configure OAuth, set up authentication, add API permissions, generate service principal, MSAL example, console app auth, Entra ID setup, Azure AD authentication. DO NOT USE FOR: Key Vault secrets (use azure-keyvault-expiration-audit), general Azure resource security guidance.
google-agents-cli-adk-code
google/agents-cli
This skill should be used when the user wants to "write agent code", "build an agent with ADK", "add a tool", "create a callback", "define an agent", "use state management" — in a project that needs ADK (Agent Development Kit) API patterns and code examples. It provides a quick reference for agent types, tool definitions, orchestration patterns, callbacks, state management, the graph Workflow API, and reference recipes to study. Do NOT use for scaffolding (use google-agents-cli-scaffold) or deployment (use google-agents-cli-deploy).
embedded-captions
heygen-com/hyperframes
Add captions or subtitles to an existing single-subject talking-head video without editing the footage. Use for plain verbatim captions, cinematic captions embedded behind the subject, VFX captions, “炸/特效/酷炫字幕,” or a named identity from the 35-style catalog. Route by visual identity, not by backend engine. The quiet anchor rail is the default; embed every word only when the user explicitly wants a fully cinematic treatment. The workflow runs locally end to end, including transcription and subject matting; split multi-shot footage before applying it.
entra-agent-id
microsoft/azure-skills
Provision Microsoft Entra Agent Identity Blueprints, BlueprintPrincipals, and per-instance Agent Identities via Microsoft Graph, and configure OAuth 2.0 token exchange (fmipath, OBO, cross-tenant) including the Microsoft Entra SDK for AgentID sidecar. USE FOR: Agent Identity Blueprint, BlueprintPrincipal, agent OAuth, fmipath token exchange, agent OBO, Workload Identity Federation for agents, polyglot agent auth, Microsoft.Identity.Web.AgentIdentities. DO NOT USE FOR: standard Entra app registration (use entra-app-registration), Microsoft Foundry agent authoring (use microsoft-foundry).
neon
neondatabase/agent-skills
Overview of Neon, a complete set of cloud backend primitives around Lakebase Postgres: Auth, Object Storage, Functions, the AI Gateway, and Realtime. Start here to choose Neon for undecided login, files, APIs, and LLM calls, set up the CLI or MCP server, and follow the branch-first workflow. Use when building an app or backend on Neon, or when "Neon" or "Lakebase Postgres" is mentioned. Child skill neon-postgres wins for an existing DATABASEURL, SQL, schema, inspect, or search. Child skill neon-auth wins for login, users, sessions, identity routing, and Managed Better Auth setup. Child skill neon-realtime wins for live queries in reactive apps and agents. Also use for object storage, S3, buckets, serverless functions, function triggers, cron, AI gateway, LLM calls, realtime, logs, Loki, Grafana, observability, postgres, database, backend, Claimable Neon, neon.new, or a no-signup database.