add-model
Skill84 starsChanged 7 months agoMITView on GitHub
Add a new model to a live LiteLLM proxy. Walks the user through picking a provider, entering the deployment name and credentials, calls POST /model/new, then test-calls the model to confirm it routes correctly. Use when the user wants to add, register, deploy, or configure a new model on a LiteLLM proxy instance.
- Reads credentials
- Sends data out
13 other projects use a version of this.
Adopted by
Most recently taken up by
- theopenco/llmgatewaytheir own version, first seen Nov 6, 2026
- KevinArce/create-bun-apitheir own version, first seen Oct 25, 2026
- whitecircle/halotheir own version, first seen Oct 9, 2026
- guoqingbao/vllm.rstheir own version, first seen Oct 8, 2026
- autogluon/tabarenatheir own version, first seen Oct 8, 2026
- Ame-Al/ametheir own version, first seen Oct 8, 2026
Other versions13 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 13
- simstudioai/sim★ 30ksame name
- netbox-community/netbox★ 22ksame name
- theopenco/llmgateway★ 1.7ksame name
- Pipelex/pipelex★ 949same name
- whitecircle/halo★ 851same name
- adaline/gateway★ 606same name
- giselles-ai/giselle★ 560same name
- autogluon/tabarena★ 363same name
- guoqingbao/vllm.rs★ 345same name
- KevinArce/create-bun-api★ 11same name
3 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository20 other files it gives its agents.
- add-agentSkill
- add-keySkill
- add-mcpSkill
- add-orgSkill
- add-teamSkill
- add-userSkill
- delete-agentSkill
- delete-keySkill
- delete-mcpSkill
- delete-modelSkill
- delete-orgSkill
- delete-teamSkill
- delete-userSkill
- update-agentSkill
- update-keySkill
- update-mcpSkill
- update-modelSkill
- update-teamSkill
- update-userSkill
- view-usageSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Add a new LLM to a live LiteLLM proxy.
- Distinctive: line 18
Ask for these if not already known:
- Distinctive: line 67
After adding, verify it routes:
“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Add Model
Add a new LLM to a live LiteLLM proxy.
Setup
Ask for these if not already known:
LITELLM_BASE_URL — e.g. https://my-proxy.example.com
LITELLM_API_KEY — proxy admin keyAPI reference: https://litellm.vercel.app/docs/proxy/model_management
Ask the user
- Public model name — what callers will send in
"model": "..."(e.g.gpt-4o,my-claude,llama3) - Provider — pick from the table below
- Credentials — whatever that provider needs
Provider table
| Provider | litellm_params.model | Extra params |
| OpenAI | openai/gpt-4o | api_key |
| Azure OpenAI | azure/<deployment-name> | api_key, api_base, api_version |
| Anthropic | anthropic/claude-3-5-sonnet-20241022 | api_key |
| AWS Bedrock | bedrock/anthropic.claude-3-5-sonnet-20241022-v2:0 | AWS creds via env |
| Google Vertex | vertex_ai/gemini-1.5-pro | vertex_project, vertex_location |
| Ollama | ollama/llama3 | api_base (e.g. http://localhost:11434) |
| Groq | groq/llama-3.3-70b-versatile | api_key |
| Together AI | together_ai/meta-llama/Llama-3-70b | api_key |
| Mistral | mistral/mistral-large-latest | api_key |
Full list: https://docs.litellm.ai/docs/providers
Run
curl -s -X POST "$BASE/model/new" \
-H "Authorization: Bearer $KEY" \
-H "Content-Type: application/json" \
-d '{
"model_name": "<public-name>",
"litellm_params": {
"model": "<provider/deployment>",
"api_key": "<key>",
"api_base": "<base_if_needed>",
"api_version": "<version_if_azure>"
}
}'Test it
After adding, verify it routes:
curl -s -X POST "$BASE/chat/completions" \
-H "Authorization: Bearer $KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "<public-name>",
"messages": [{"role": "user", "content": "say hi"}],
"max_tokens": 10
}'Output
Show model_id from the response — needed to update or delete the model later.
Report pass/fail from the test call.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

