Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Show API pricing in the /model catalogue

Open
#914 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
65/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Domain
cli

Research direction

Start with the /model picker and the cmd --list-models entry point, then trace the billing source of truth used by the docs pricing page. Done means each model exposes its $/1M input, output, and cache rates in the catalogue without changing the underlying billing data.

Written by the indexing model from the issue text.

Description

Feature Description

opening the /model picker or running cmd --list-models only gives you names, descriptions, context windows and effort levels. the per-1M-token rates (input/output/cache) already exist in the billing source of truth, the docs pricing page shows them, but nothing in the product surfaces them. please show pricing alongside each model in the /model catalogue.

Use Case

comparing models mid-session, like picking between mimo-v2.6-flash, a free model such as poolside/laguna-s-2.1-free, and a frontier model, currently means alt-tabbing to the docs pricing page. seeing $/1M in/out and cache rates right in the picker would make the choice a one-step decision.

Additional Context

this is a display-only change, the rates are already resolved from the billing source of truth for the docs. it could live in the model's detail pane when selected, or as an extra column in the picker.

How important is this to you?

None

Dominant language
No language data
Stars
4k
Forks
350
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CommandCodeAI/command-code

All issues in CommandCodeAI/command-code

Similar issues

More CLI issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.