update-model
Skill84 starsChanged 7 months agoMITView on GitHub
Update an existing model on a live LiteLLM proxy. Ask for the model_id and what to change (API key, base URL, etc.), then call POST /model/update.
- Reads credentials
- Sends data out
In this repository20 other files it gives its agents.
- add-agentSkill
- add-keySkill
- add-mcpSkill
- add-modelSkill
- 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-teamSkill
- update-userSkill
- view-usageSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Update an existing model's configuration on a live LiteLLM proxy.
- Very specific: line 56
Only include litellm_params fields being changed.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Update Model
Update an existing model's configuration on a live LiteLLM proxy.
Setup
LITELLM_BASE_URL — e.g. https://my-proxy.example.com
LITELLM_API_KEY — proxy admin keyAsk the user
- model_id (required) — if they don't have it, list models first:
curl -s "$BASE/model/info" -H "Authorization: Bearer $KEY" | python3 -c " import sys,json for m in json.load(sys.stdin).get('data',[]): print(m['model_info']['id'], m['model_name']) " - What to change — any combination of:
api_key(rotate the credential)api_base(change endpoint)api_version(Azure)model(underlying model string, e.g.azure/new-deployment)
Run
curl -s -X POST "$BASE/model/update" \
-H "Authorization: Bearer $KEY" \
-H "Content-Type: application/json" \
-d '{
"model_info": {"id": "<model_id>"},
"litellm_params": {
"api_key": "<new_key>",
"api_base": "<new_base>"
}
}'Only include litellm_params fields being changed.
Output
Confirm the model was updated. Offer to run a test call to verify it still routes correctly.
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.

