llm-provider SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
llm-provider from caliber-ai-org/ai-setup is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add caliber-ai-org/ai-setup/llm-provider@git:20260428.99f2785Pins git:20260428.99f2785 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- caliber-ai-org/ai-setup
- Path
.cursor/skills/llm-provider/SKILL.md- Versions recorded
- 4
- Latest version
- git:20260428.99f2785, committed Apr 28, 2026
- First version recorded
- Mar 29, 2026
- Size
- 10,796 bytes
- Repository stars
- 1,316
- License
- MIT
Adds a new LLM provider implementing LLMProvider interface with call() and stream() methods. Integrates with provider factory in src/llm/index.ts, config detection in src/llm/config.ts, and error handling via tracking and recovery. Use when adding a new model backend, integrating a third-party LLM API, or extending LLM platform support. Do NOT use for fixing bugs in existing providers, modifying existing provider behavior, or changing the LLMProvider interface.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# LLM Provider
## Critical
1. **All providers MUST implement the LLMProvider interface** from src/llm/types.ts with three methods:
- call(options: LLMCallOptions): Promise<string> — single non-streaming call returning text
- stream(options: LLMStreamOptions, callbacks: LLMStreamCallbacks): Promise<void> — streaming call invoking callbacks
- listModels?(): Promise<string[]> — optional; list available models from the API
2. **Initialize client in constructor and store defaultModel from config**. Example: `this.client = new YourSDK({ apiKey: config.apiKey })`. Never lazy-initialize on first call — providers are instantiated once and cached in src/llm/index.ts.
3. **For EVERY response in call() and stream(), invoke trackUsage(model, usage)** from src/llm/usage.js before returning/ending. This is mandatory — it captures token metrics for CLI telemetry and cost analysis. If the API doesn't return usage data, estimate via estimateTokens(text), which assumes ~4 chars per token.
…Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_logdyhh7i4ba3fuj/f0668eaedf386c2938cec64947b86b7526a783aa42e1b79c9cc06d33db8293c1.json
Then /plugin install llm-provider@markdownregistry-logdyhh7i4ba3fuj in Claude Code. It installs git:20260428.99f2785, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add caliber-ai-org/ai-setup/llm-provider@sha256:f0668eaedf386c29The line at the top of this page pins the label git:20260428.99f2785, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_logdyhh7i4ba3fuj)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in caliber-ai-org/ai-setup/llm-provider since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of llm-provider from somewhere else? Ask it: where did my llm-provider come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 4 versions of this file, between Mar 29, 2026 and Apr 28, 2026, about one every 10 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260428.99f2785 latest | 2026-04-28 | 99f2785 | 10,796 B | A | view · diff |
| git:20260425.9a46fd4 | 2026-04-25 | 9a46fd4 | 5,503 B | A | view · diff |
| git:20260424.9b749cd | 2026-04-24 | 9b749cd | 10,853 B | A | view · diff |
| git:20260329.8cf93fd | 2026-03-29 | 8cf93fd | 5,694 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/llm-provider/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (10796 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
caliber-ai-org/ai-setup · 1,316 stars · license MIT · pushed 2026-09-24 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_logdyhh7i4ba3fuj GET https://markdownregistry.com/api/v1/resolve?ref=caliber-ai-org/ai-setup/llm-provider GET https://markdownregistry.com/api/v1/blob/f0668eaedf386c2938cec64947b86b7526a783aa42e1b79c9cc06d33db8293c1
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from caliber-ai-org/ai-setup
Every file in caliber-ai-org/ai-setup
Other files named llm-provider
Browse by kind, by grade A, or by owner.
Kept in .cursor/skills, the folder Cursor reads. More agent skills for Cursor.