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 xberg-io/liter-llm --skill liter-llm-calling-llmsgit clone --depth 1 https://github.com/xberg-io/liter-llmWrote 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/xberg-io/liter-llm/liter-llm-calling-llms)<a href="https://agentmods.dev/skills/xberg-io/liter-llm/liter-llm-calling-llms"><img src="https://agentmods.dev/badge/skills/xberg-io/liter-llm/liter-llm-calling-llms/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/xberg-io/liter-llm/liter-llm-calling-llms"><img src="https://agentmods.dev/badge/skills/xberg-io/liter-llm/liter-llm-calling-llms.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.00044 | $0.00744 |
| Opus 5.5 | $0.00018 | $0.00298 |
| Sonnet 5.5 | $0.00009 | $0.00149 |
| Haiku 4.5 | $0.00004 | $0.00074 |
Grade A, and why
liter-llm-calling-llms scanned grade A with 0 findings 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 5d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Calling LLMs
Build a ChatCompletionRequest and send it with client.chat(request). Create
the client with create_client(...). The model string is provider/model; the
prefix selects the backend.
import asyncio, json, os
from liter_llm import create_client
from liter_llm._internal_bindings import ChatCompletionRequest
async def main() -> None:
client = create_client(api_key=os.environ["OPENAI_API_KEY"])
request = ChatCompletionRequest.from_json(json.dumps({
"model": "openai/gpt-4o",
"messages": [
{"role": "system", "content": "You are concise."},
{"role": "user", "content": "Name three Rust crates for HTTP."},
],
}))
response = await client.chat(request)
print(response.choices[0].message.content)
asyncio.run(main())
Provider routing
The model string's prefix selects the provider; build a request per backend:
ChatCompletionRequest.from_json('{"model":"anthropic/claude-sonnet-4-20250514","messages":[...]}')
ChatCompletionRequest.from_json('{"model":"gemini/gemini-2.0-flash","messages":[...]}')
ChatCompletionRequest.from_json('{"model":"groq/llama3-70b","messages":[...]}')
ChatCompletionRequest.from_json('{"model":"mistral/mistral-large-latest","messages":[...]}')
ChatCompletionRequest.from_json('{"model":"bedrock/anthropic.claude-v2","messages":[...]}')
Set a full provider/model as model_hint at construction to select the client
provider and credential source. Requests without a recognized prefix fall back to
that client provider:
client = create_client(api_key=os.environ["OPENAI_API_KEY"], model_hint="openai/gpt-4o")
# the request model can now omit the provider prefix:
request = ChatCompletionRequest.from_json('{"model":"gpt-4o","messages":[...]}')
await client.chat(request) # routes to OpenAI
Notes
- Keys come from env vars (
OPENAI_API_KEY,ANTHROPIC_API_KEY, …); never hardcode them. - Without a recognized prefix, requests fall back to the client's configured provider;
a client without
model_hintdefaults to OpenAI. - Environment credentials are selected when constructing the client, not independently
for every request. Use a separate client with matching
model_hintand credentials for each provider. A prefix changes routing but does not switch the client's API key. - Python errors are typed exceptions exported from
liter_llm:AuthenticationError,RateLimitedError,BadRequestError,ContextWindowExceededError,ContentPolicyError,NotFoundError,ServerError,ServiceUnavailableError,LiterLlmTimeoutError,BudgetExceededError— all subclasses ofLiterLlmError.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 75 lines · 44 tokens per session scan A c39b67b4c86a
liter-llm-calling-llms is a skill published in the GitHub repository xberg-io/liter-llm (261 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 744 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-15.
Other skills, from other repositories
pydantic-ai
Build production-ready AI agents with PydanticAI — type-safe tool use, structured outputs, dependency injection, and multi-model support.
ml-expert
Expert-level machine learning, deep learning, model training, and MLOps. Use when the user mentions machine learning, deep learning, neural networks, MLOps, or data science, or when the task involves Machine Learning Fundamentals, Data Preparation, or Model Training.
openai-patterns
Production OpenAI API patterns — model selection, prompt engineering, function calling, streaming, error handling, cost control, and structured outputs.
pydantic-ai
Build production-ready AI agents with PydanticAI — type-safe tool use, structured outputs, dependency injection, and multi-model support.
multi-llm-routing
Multi-LLM routing authority — provider selection, cost-aware tiering, fallback chains, latency budgets, health checks, A/B model testing, and unified client abstraction across Anthropic/OpenAI/Mistral.
mle-workflow
Production machine-learning engineering workflow for data contracts, reproducible training, model evaluation, deployment, monitoring, and rollback. Use when building, reviewing, or hardening ML systems beyond one-off notebooks.