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

How to audit which model ran each agent step and what it cost with Hi Route

Check per-session model, usage and cost so you can tune routing with real execution data.

Who it is forA developer or team lead who suspects routing is not saving money and needs evidence from actual sessions.

The problemWithout per-step records, it is unclear which model handled each turn, how much usage it used, and whether routing changed the outcome.

The outcomeA list of sessions showing the task category, actual model group, tool outcomes, usage and cost, which you can use to adjust the routing plan.

What you need first

  • macOS 15 or later on Apple silicon or Intel, or Linux x86_64 or ARM64 (aarch64) for the headless CLI and daemon
  • An existing Codex or Claude Code subscription, a registered API, or a compatible custom API to connect
  • A decision model connection (Bailian, OpenRouter Jev, TypeSafe, or a compatible endpoint) for model-based judgment
  • An Agent client such as Codex or Claude Code configured to use HiRoute

Steps

  1. Run hiroute service start --output json if the service is not running, then run hiroute system status --output json to confirm.
  2. Run agent sessions through your connected Agent client as usual.
  3. Open the sessions view in Hi Route and filter for a recent session.
  4. Check the task category, actual model group, usage and cost recorded for each turn.
  5. Adjust the difficulty routing thresholds or custom branches in the routing plan based on what you see.

Prompt for your agent

Using the HiRoute repo at https://github.com/higress-group/HiRoute, review the most recent session for <target agent client> and list each turn's task category, actual model group, usage and cost. Verify that the model shown is the one that actually ran, not the one the routing plan intended.

Caveat. The README describes the session and cost views in general terms, so exact field names and export options may differ from what you see in the app.

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