Back to Skills

byok-custom-model

Register a custom LLM endpoint with your own API key for chat in Starchild. Use when adding a personal Anthropic, OpenAI, Grok, Qwen, DeepSeek, NEAR AI, or Venice key as a chat model (e.g. add my Claude key, register DeepSeek).

17stars9forksUpdated 6/27/2026

Security Assessment

Low Risk(80/100)

Detected risks:

Sensitive File Access([SKILL.md] .env)
Security Score80/100

About byok-custom-model

Registers a custom LLM endpoint with a user-supplied API key so it appears as a selectable chat model in Starchild, bypassing the platform proxy and calling the vendor or aggregator directly. It is a script-mode skill with no registered tools: the agent reads the file and then calls Python exports from a bash block. The skill ships with eleven pre-configured vendor presets — including Anthropic, OpenAI, xAI/Grok, Qwen/DashScope, DeepSeek, Kimi/Moonshot, MiMo, Gemini, Gemma, NEAR AI, and Venice — each with base_url, wire format, thinking parameters, and capabilities already filled in.

The onboarding flow is templates-first. The user's intent is matched against the curated vendor table before asking for any URL, and a match goes straight to add_template(vendor=...). Only when no curated vendor fits does the flow ask the user to paste the provider's official API example (without a real key), run parse_example to auto-detect base_url, upstream_model, wire (openai vs anthropic), thinking params, and vendor-specific request fields, and then call add(...). Whenever add() or add_template() returns a need_env_input field, the agent must immediately call the request_env_input tool, which pops a secure-input UI so the key lands in workspace/.env; the script cannot pop that UI itself. The exported functions include templates, list_vendor_models, add_template, parse_example, add, list_models, get, and remove, each returning a dict with ok True or ok False and an error.

Security rules are strict: API keys pasted in chat are refused, the secure popup is the only accepted channel, the popup is never re-issued automatically while waiting, and custom_models.yaml and .env are never hand-edited. After registration the model appears prefixed with custom/ and is selected with /model custom/<name>, with vendor pricing applied directly to the user's BYOK quota. A privacy-first tier favors NEAR AI for its shorter hardware-enclave trust chain and recommends TEE-protected models there; the skill also documents NEAR's reasoning protocol, which nests chat_template_kwargs under extra_body rather than using top-level reasoning parameters.

FAQ

How many vendors come pre-configured, and which path should I use for them?

Eleven curated vendors ship pre-configured (Anthropic, OpenAI, xAI, Qwen, DeepSeek, Kimi, MiMo, Gemini, Gemma, NEAR AI, Venice). For any of these, always use add_template(vendor=...) rather than parse_example plus add, since base_url, wire, thinking, and capabilities are already filled in.

How are API keys handled securely?

Keys are never accepted pasted in chat. When add or add_template returns a need_env_input field, the agent must call the request_env_input tool, which opens a secure-input UI; the key is written to workspace/.env. If a user pastes a key, the skill refuses and directs them to the secure popup.

What do I do if no curated vendor matches my provider?

Ask the user to paste the provider's official API example (with placeholder rather than real keys), run parse_example to auto-detect base_url, model, wire format, and thinking params, review the draft, then call add(...). This custom path is intended for self-hosted or rare providers.

How does a registered model get used after setup?

The model appears in the selector prefixed with custom/, and the user switches to it via /model custom/<name> or the model picker UI. Subsequent calls bypass the platform proxy, so the vendor's pricing applies directly to the user's BYOK quota.

Why does the skill favor NEAR AI for privacy-sensitive users?

Both NEAR AI and Venice target privacy, but NEAR AI is the cleaner integration with a shorter trust chain because Venice's TEE story is itself built on NEAR AI plus Phala. The curated NEAR list is TEE-protected open-weight models only, and the skill recommends staying on a TEE-protected model since the hardware enclave is the whole privacy value.

All Files

2 files
exports.py17.7 KB
View
SKILL.md8.5 KB
View

Install byok-custom-model

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill