DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to compare model token prices before picking a model with DSH Cost Meter

Check per-token rates and update times for OpenRouter and multi-vendor models, and sync official prices.

  • Money
  • Beginner
  • 15 minutes
  • From the README
  • Any agent

Who it is forA developer choosing between several models who wants current token rates before starting a task.

The problemRates differ across vendors and change over time, and checking each provider's pricing page is slow.

The outcomeYou can hover a model in the picker to see its token rates and update time, or search the full catalog in Settings → Cost → Prices.

What you need first

  • DeepSeek Harness (DSH) version 0.2.0 or later installed
  • The dsh-cost-meter plugin installed from the README Installation section
  • Provider keys or accounts only for the balance and quota sources you want to query

Steps

  1. Open the model picker in DSH and hover a model to see its token rates and update time.
  2. Open Settings → Cost → Prices to search the full catalog.
  3. Look for price-change markers in the table and follow the official model links for details.
  4. Use the one-click price sync from the official docs when you want the latest table.

Prompt for your agent

Using the dsh-cost-meter plugin in DeepSeek Harness 0.2.0 or later, search the price catalog in Settings → Cost → Prices for <model name> and report its input and output token rates and last update time. Verify the rates against the official model link shown in the table.

Caveat. The README says the OpenRouter price view needs no API key, but the built-in catalog can lag the official docs until you run a sync.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page