Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add BerriAI/litellm-skills --skill update-agentgit clone --depth 1 https://github.com/BerriAI/litellm-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/berriai/litellm-skills/update-agent)<a href="https://agentmods.dev/skills/berriai/litellm-skills/update-agent"><img src="https://agentmods.dev/badge/skills/berriai/litellm-skills/update-agent/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/berriai/litellm-skills/update-agent"><img src="https://agentmods.dev/badge/skills/berriai/litellm-skills/update-agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00045 | $0.00354 |
| Opus 5.5 | $0.00018 | $0.00142 |
| Sonnet 5.5 | $0.00009 | $0.00071 |
| Haiku 4.5 | $0.00005 | $0.00035 |
Grade A, and why
update-agent scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
compatibility: Requires curl. What it actually says
Update Agent
Update an existing AI agent on a live LiteLLM proxy.
Setup
LITELLM_BASE_URL — e.g. https://my-proxy.example.com
LITELLM_API_KEY — proxy admin key
Ask the user
- agent_id — if they don't have it, list first:
curl -s "$BASE/v1/agents" -H "Authorization: Bearer $KEY" - What to change — any combination of:
model(swap the underlying model)descriptiontpm_limit/rpm_limit- MCP server access
Run
Use PATCH to update only the changed fields:
curl -s -X PATCH "$BASE/v1/agents/<agent_id>" \
-H "Authorization: Bearer $KEY" \
-H "Content-Type: application/json" \
-d '{
"litellm_params": {"model": "<new_model>"},
"agent_card_params": {"description": "<new_description>"}
}'
Output
Show the updated agent name, model, and description. Confirm the agent ID is unchanged.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 54 lines · 45 tokens per session scan A bfe9b9f8c795
update-agent is a skill published in the GitHub repository BerriAI/litellm-skills (99 stars, last pushed 5mo ago), licensed MIT. It adds 45 tokens to every session and 354 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…