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

How to watch context, cost and subagents in a live dashboard with Awesome Claude Code Mods

Use flightdeck to see context use, cost, permission checks and subagents while Claude works.

Authorization notice. Awesome Claude Code Mods is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Remote script. A dashboard mod still runs third-party code in your session, so check its access details before installing.

Who it is forA developer running long Claude Code sessions with subagents who wants to see context and spend as they grow.

The problemLong sessions hide how much context and cost has built up, and subagent work is hard to follow.

The outcomeA live dashboard that shows context, cost, permission checks and subagents, without changing tool calls.

What you need first

  • Claude Code 2.1.287 or later
  • Node 18 or later for mod-finder
  • A Claude Code terminal session
  • Access details reviewed for any mod before you install it

Steps

  1. Run /plugin install mod-finder --marketplace karanb192/awesome-claude-code-mods and complete the installation prompts.
  2. Run /reload-plugins.
  3. Ask Claude: Find a mod that shows context and cost in a live dashboard.
  4. Open flightdeck's access details and its demo, then follow its installation instructions.
  5. Check the dashboard during a session to confirm context, cost and subagents appear.

Prompt for your agent

Using the karanb192/awesome-claude-code-mods repo, find the flightdeck mod and summarize what it shows and what access it reports. Expected output: a list of dashboard items (context, cost, permission checks, subagents) and the access details. Verify that the README states it does not change tool calls before recommending it.

Caveat. The README describes the dashboard only through its demo and summary, so confirm the exact display in your own session.

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