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

How to find where a Claude Code session spends time and context with My Claude Code Mods

Install two analysis mods to see time split by source and flag repeated or wasted context.

Credentials. Profiler traces and context reports can contain session content, so check them before sharing or exporting them to a shared tracing backend.

Who it is forA developer whose Claude Code sessions feel slow or run out of context, and who wants evidence before changing their workflow.

The problemLong sessions hide where time goes between model waits, tool calls, subagents, and re-reads, and what fills the context window.

The outcomeA clearer picture of time and context use per session, with advice on what to change.

What you need first

  • A Claude Code CLI with Mods support (mods are enabled by default from 2.1.287)
  • git on your PATH for Time Machine
  • A terminal running macOS, Linux, or a Bash or Zsh shell for the install block
  • Node 22.19.0 or later only if you plan to run the repo's development tests

Steps

  1. Add the marketplace once with claude plugin marketplace add YeonwooSung/my-claude-code-mods.
  2. Install both mods with claude plugin install agent-profiler@my-claude-code-mods --scope user and claude plugin install context-inspector@my-claude-code-mods --scope user.
  3. Start a new Claude Code session, or run /reload-plugins in an open session, then run /plugin to confirm both mods are loaded.
  4. Work through a real task, then read the agent-profiler and context-inspector READMEs linked under Mods to learn how to view each report.
  5. Optionally export OTLP traces for Jaeger or Tempo, as described in the agent-profiler README.

Prompt for your agent

Using the repo YeonwooSung/my-claude-code-mods, install agent-profiler and context-inspector at user scope, then run a session on <task description>. Report where time went (model wait, tools, subagents, re-reads) and which context items were flagged as waste, citing the specific tool calls or files. Verify that every cited item appears in the session output before you finish.

Caveat. The README says Context Inspector lacks session.append on the early-access 2.1.280 build, so use a current Claude Code CLI for full results.

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