Skill

compare-models

Compares Replicate models by cost, speed, quality, and capabilities using schemas, test predictions, metrics, and docs. Useful for selecting optimal AI models.

OpenAPI

ai-ml

npx claudepluginhub replicate/skills --plugin prompt-images

Tool Access

This skill uses the workspace's default tool permissions.

Preview

- Reference: <https://replicate.com/docs/llms.txt>

SKILL.md

Similar Skills

model-comparator

Compares AI and LLM models on benchmarks, capabilities, cost, latency, context window, and task-specific fit to help select optimal models for production use cases and budgets.

nickcrew-claude-ctx-plugin

find-models

Finds AI models on Replicate using search queries and curated collections, fetches input/output schemas, and guides selection of official, recent models by tags and run counts.

replicate

openrouter-models

125

Queries OpenRouter for 300+ AI models' pricing, context lengths, capabilities, throughput, provider latency/uptime. Scripts to list, search, compare, resolve names, find optimal providers.

9 files

openrouter

Stats

Stars30

Forks2

Last CommitApr 17, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Docs

Reference: https://replicate.com/docs/llms.txt
OpenAPI schema: https://api.replicate.com/openapi.json
MCP server: https://mcp.replicate.com
Per-model docs: https://replicate.com/{owner}/{model}/llms.txt
Set Accept: text/markdown when requesting docs pages for Markdown responses.

Workflow

Search or browse collections to build a shortlist of candidate models.
Fetch each model's schema to compare inputs, outputs, and capabilities.
Check pricing from model metadata or the Replicate website.
Run a small batch of test predictions to compare output quality.
Pick the model that best fits your constraints (cost, latency, quality).

What to compare

Speed: Check metrics.predict_time on completed predictions for actual inference time. Official models are always warm. Community models can cold-boot.
Cost: Official models have predictable per-run pricing. Community models charge by compute time (GPU-seconds). Run a few predictions and check the metrics field for actual cost.
Quality: Run the same prompts through each model and compare outputs. Quality is subjective. Match it to your use case, not a leaderboard.
Capabilities: Compare input schemas for supported features (reference images, masks, aspect ratios, streaming, multi-image input). Check output formats.

Key tradeoffs

Lowest cost: smaller/distilled models. Accept slower inference and lower quality.
Lowest latency: official models or schnell/turbo variants. Accept higher cost per run.
Highest quality: pro/max/quality variants. Accept slower inference and higher cost.
Most control: models with ControlNet, masks, or reference images. Accept more complex input setup.

Official vs community models

Official models: always warm, stable APIs, predictable pricing, maintained by Replicate.
Community models: may cold-boot, require version pinning, maintained by the author.
If a community model meets your needs and an official model doesn't, consider creating a deployment for consistent uptime.

Prompting guidance

For prompting techniques and task-specific guidance:

Image generation and editing: see the prompt-images skill.
Video generation: see the prompt-videos skill.