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

How to find which sub-agent uses the most tokens with Agent Standup

Read the per-agent ⚡ token counter to see which sub-agent is the expensive one in a session.

Who it is forA developer or team lead who needs to control the cost of a multi-agent Claude Code session.

The problemA session with a lead and many sub-agents hides which one spends the most tokens.

The outcomeEach agent shows its token count, with the model that spent it when a session mixes models.

What you need first

  • Node 18 or newer for the npx command, or VS Code for the extension
  • At least one Claude Code, Codex or Mistral Vibe session on this machine, or use the built-in demo

Steps

  1. Run npx @double_geste/agent-standup@latest --open and open the live call for your session.
  2. Read the ⚡ counter in the header and on each agent tile.
  3. Hover over the counter to see cache reads, shown separately from input, output and cache writes.
  4. Compare the agents list entries to find the sub-agent with the highest count.

Prompt for your agent

In the repo Atoll92/agent-standup, open the live call for my Claude Code session and list each agent with its ⚡ token count and model. Identify the agent with the highest count. Verify that the figures match the token counts recorded in the session files, noting that they are not an estimate of the bill.

Caveat. The counts are read from the session files as recorded by Claude Code and are not an estimate of your bill.

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