agentleFS
BerriAIBerriAI/litellm-skills/add-model/SKILL.md

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

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
  1. Distinctive:

    Add a new LLM to a live LiteLLM proxy.

    line 14
  2. Distinctive:

    Ask for these if not already known:

    line 18
  3. Distinctive:

    After adding, verify it routes:

    line 67

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 key

API reference: https://litellm.vercel.app/docs/proxy/model_management

Ask the user

  1. Public model name — what callers will send in "model": "..." (e.g. gpt-4o, my-claude, llama3)
  2. Provider — pick from the table below
  3. Credentials — whatever that provider needs

Provider table

Providerlitellm_params.modelExtra params
OpenAIopenai/gpt-4oapi_key
Azure OpenAIazure/<deployment-name>api_key, api_base, api_version
Anthropicanthropic/claude-3-5-sonnet-20241022api_key
AWS Bedrockbedrock/anthropic.claude-3-5-sonnet-20241022-v2:0AWS creds via env
Google Vertexvertex_ai/gemini-1.5-provertex_project, vertex_location
Ollamaollama/llama3api_base (e.g. http://localhost:11434)
Groqgroq/llama-3.3-70b-versatileapi_key
Together AItogether_ai/meta-llama/Llama-3-70bapi_key
Mistralmistral/mistral-large-latestapi_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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.