How do I install the Modelinfo CLI skill?

Run npx skillmds@latest add zerob13/modelinfo-cli in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Modelinfo CLI safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Modelinfo CLI?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Modelinfo CLI free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Modelinfo CLI?

zerob13 (@zerob13) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Modelinfo CLI by zerob13 — Agent Skill

Name: Modelinfo CLI
Author: zerob13

Modelinfo CLI

Use when Codex needs to inspect, search, compare, or troubleshoot AI model metadata with the published modelinfo CLI. Trigger for tasks such as looking up a model, searching by keyword, listing providers, listing models under a provider, comparing two models, checking cache/update state, or producing JSON output from modelinfo commands. Use global `modelinfo`, `bunx modelinfo`, or `npx modelinfo`.

zerob13 1806d0b 2 files · 2.8 KB Updated Sep 17, 2026

File contents

modelinfo CLI

Run the CLI instead of guessing model metadata.

Choose the execution path

Prefer modelinfo ... when the CLI is already installed globally.
Prefer bunx modelinfo ... for normal usage against the published package.
Use npx modelinfo ... when Bun is unavailable but the published package should still be used.

Start with these commands

Inspect one model: modelinfo <model> or bunx modelinfo <model>
Inspect one model with provider filter: modelinfo <model> --provider <provider>
Search models: modelinfo search <keyword>
Search as JSON: modelinfo search <keyword> --output json
List providers: modelinfo providers
List one provider's models: modelinfo list <provider>
Compare two models: modelinfo diff <modelA> <modelB>
Show capabilities only: modelinfo caps <model>
Show pricing only: modelinfo cost <model>
Show limits only: modelinfo limit <model>
Refresh local cache: modelinfo update
Inspect cache health: modelinfo doctor

Resolve ambiguity correctly

Do not assume model_id is unique across providers.
If a lookup returns multiple rows, rerun with --provider <provider>.
For diff, use --provider-a and --provider-b when either side is ambiguous.
Prefer --output json when the user wants structured data, exact fields, or follow-up processing.

Use JSON output for agent workflows

Single model: modelinfo <model> --provider <provider> --output json
Search results: modelinfo search <keyword> --provider <provider> --output json
Provider model list: modelinfo list <provider> --output json
Cache status: modelinfo doctor --output json
Update summary: modelinfo update --output json

Minimal workflow

If the user asks about one model, run modelinfo <model> first, or bunx modelinfo <model> if the CLI is not installed.
If the result is ambiguous, rerun with --provider or present the candidate rows.
If the user needs machine-readable output, rerun the same command with --output json.
If the cache looks stale or missing, run modelinfo doctor, then modelinfo update if needed.

---name: modelinfo-clidescription: Use when Codex needs to inspect, search, compare, or troubleshoot AI model metadata with the published modelinfo CLI. Trigger for tasks such as looking up a model, searching by keyword, listing providers, listing models under a provider, comparing two models, checking cache/update state, or producing JSON output from modelinfo commands. Use global `modelinfo`, `bunx modelinfo`, or `npx modelinfo`.---# modelinfo CLIRun the CLI instead of guessing model metadata.## Choose the execution path- Prefer `modelinfo ...` when the CLI is already installed globally.- Prefer `bunx modelinfo ...` for normal usage against the published package.- Use `npx modelinfo ...` when Bun is unavailable but the published package should still be used.## Start with these commands- Inspect one model: `modelinfo <model>` or `bunx modelinfo <model>`- Inspect one model with provider filter: `modelinfo <model> --provider <provider>`- Search models: `modelinfo search <keyword>`- Search as JSON: `modelinfo search <keyword> --output json`- List providers: `modelinfo providers`- List one provider's models: `modelinfo list <provider>`- Compare two models: `modelinfo diff <modelA> <modelB>`- Show capabilities only: `modelinfo caps <model>`- Show pricing only: `modelinfo cost <model>`- Show limits only: `modelinfo limit <model>`- Refresh local cache: `modelinfo update`- Inspect cache health: `modelinfo doctor`## Resolve ambiguity correctly- Do not assume `model_id` is unique across providers.- If a lookup returns multiple rows, rerun with `--provider <provider>`.- For `diff`, use `--provider-a` and `--provider-b` when either side is ambiguous.- Prefer `--output json` when the user wants structured data, exact fields, or follow-up processing.## Use JSON output for agent workflows- Single model: `modelinfo <model> --provider <provider> --output json`- Search results: `modelinfo search <keyword> --provider <provider> --output json`- Provider model list: `modelinfo list <provider> --output json`- Cache status: `modelinfo doctor --output json`- Update summary: `modelinfo update --output json`## Minimal workflow1. If the user asks about one model, run `modelinfo <model>` first, or `bunx modelinfo <model>` if the CLI is not installed.2. If the result is ambiguous, rerun with `--provider` or present the candidate rows.3. If the user needs machine-readable output, rerun the same command with `--output json`.4. If the cache looks stale or missing, run `modelinfo doctor`, then `modelinfo update` if needed.

Frequently asked questions