PAIArtCom

Model Specs — AI skill for Claude Code

AI community

Community catalog of LLM model specs — pricing, context windows, capabilities, and AI-CLI compatibility.

How to install Model Specs

This entry records only its repository, not the path inside it, so there is no exact command to give. Open PAIArtCom/model-specs and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Model Specs does

Community catalog of LLM model specs — pricing, context windows, capabilities, and AI-CLI compatibility. Auto-synced from LiteLLM with objective corrections.

Alternatives in AI

Cc Mirror — Create multiple isolated Claude Code variants with custom providers (Z.ai, MiniMax, OpenRouter, LiteLLM) 2.1k ★
Academic Figure Skills — AI skills for academic paper figures: repo analysis, figure planning, colorblind palettes, JSON figure specs 94 ★
Datafog Python — Offline PII firewall for AI agents and LLM apps: fast local detection and redaction, Claude Code hook, LiteLLM 69 ★

README

model-specs

![model-specs hero](assets/hero.png)

A community catalog of **LLM model specifications** — pricing, context windows, capabilities, and client/CLI compatibility — kept fresh by automatically syncing [LiteLLM](https://github.com/BerriAI/litellm)'s model database and layering **objective corrections** plus data LiteLLM doesn't track (which models each AI CLI actually accepts).

If you build AI applications and keep re-implementing the same "what does this model cost / what's its context window / does this CLI accept this model id" lookups, this repo is meant to be the single source you vendor or fetch.

What's in here

Directory	What it holds	Edit by hand?
`upstream/litellm/`	A read-only mirror of LiteLLM's `model_prices_and_context_window.json`, refreshed by CI.	No — auto-synced
`patches/`	Objective corrections to the upstream data (wrong pricing, provider/platform mapping, capability flags).	Yes — via PR
`clients/`	Which model ids each AI CLI / client accepts (Claude Code, Codex, Antigravity). LiteLLM does not track this.	Yes — via PR
`dist/`	The merged, validated artifact consumers read: `catalog.json` + `catalog.sha`.	No — generated
`schema/`	JSON Schema for `dist/catalog.json`.	Yes
`scripts/`	`sync` (pull upstream), `build` (merge → dist), `validate` (schema + invariants).	Yes

**Design rule:** `upstream/` is never hand-edited. Every correction lives in `patches/` so `git diff` always shows exactly what we changed vs. what LiteLLM shipped, and the merge stays reproducible.

What's intentionally NOT here

Pricing markup / margin. This repo holds objective base costs only. Your selling price is your business policy — keep it in your own app.
Which models a given product chooses to sell. That's product config, not a community fact. Keep served-model lists in your own project.