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

What you can do with My Claude Code Mods

A set of custom Claude Code mods (plugins) that profile sessions, catch context waste and loops, record file history, and support verification and handoff work.

Trended earlier

YeonwooSung/my-claude-code-mods on GitHub

Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk.

What do you want to do?

4 use cases

  • Find where a Claude Code session spends time and context

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

    View prompt
    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.

  • Find the edit that broke a test and restore the file

    Use Time Machine's step timeline and shadow-git snapshots to locate and undo a breaking edit.

    View prompt
    In the repo YeonwooSung/my-claude-code-mods, install time-machine at user scope, then after a failing run of <test command> identify the tool call that introduced the failure. Output the step number, the file changed, and the restored content for that file. Verify the result by re-running <test command> after the restore and reporting pass or fail.

  • Catch agent retry loops before they burn your session

    Detect repeated Bash failures and edit or retry cycles with evidence and investigation prompts.

    View prompt
    Using the repo YeonwooSung/my-claude-code-mods, install loop-detective at user scope and run a session on <task description>. Report every flagged repeated Bash failure or edit/retry cycle with its evidence and the investigation prompt shown. Verify that each flagged case cites at least two matching attempts from the session before you report it.

  • Check verification, scope, and decisions before committing

    Run the workflow mods on a local checkout to review agent changes against scope and verification.

    View prompt
    In the repo YeonwooSung/my-claude-code-mods checkout, load verify-board and scope-guard with --plugin-dir and run /verify and /scope on the current changes for <task description>. Report each verification result as PASS, FAIL, STALE, or UNKNOWN and list any file outside the allowed paths. Verify that each reported file path exists in git status before you finish.

How to use My Claude Code Mods

  1. Check you have what it needs: 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.
  2. Open YeonwooSung/my-claude-code-mods on GitHub and read the README and license.
  3. Add the marketplace once with claude plugin marketplace add YeonwooSung/my-claude-code-mods.
  4. 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.
  5. Start a new Claude Code session, or run /reload-plugins in an open session, then run /plugin to confirm both mods are loaded.
  6. Work through a real task, then read the agent-profiler and context-inspector READMEs linked under Mods to learn how to view each report.

These steps come from our top use case, Find where a Claude Code session spends time and context, which also has a copy-paste agent prompt.

My Claude Code Mods alternatives · Best AI repos for Software and DevOps

About this repo

Requirements

  • 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
Maintain My Claude Code Mods? Add the Featured on Deduped badge

Paste this into your README:

[![Featured on Deduped](https://dedupedai.com/badge/yeonwoosung-my-claude-code-mods.svg)](https://dedupedai.com/use-cases/yeonwoosung-my-claude-code-mods/?ref=badge)

More badge styles and HTML

Questions about My Claude Code Mods

What is My Claude Code Mods?

A set of custom Claude Code mods (plugins) that profile sessions, catch context waste and loops, record file history, and support verification and handoff work. It is an open-source project on GitHub: https://github.com/YeonwooSung/my-claude-code-mods.

Who is My Claude Code Mods for?

Developers who use Claude Code daily and want to see where session time, tokens, and failed attempts go, or to review and hand off agent work safely.

What can I do with My Claude Code Mods?

4 use cases so far, for example: Find where a Claude Code session spends time and context; Find the edit that broke a test and restore the file; Catch agent retry loops before they burn your session. Each has steps and a copy-paste agent prompt.

What do I need to run My Claude Code Mods?

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.

What are alternatives to My Claude Code Mods?

Other hot AI repos in Software and DevOps: Harness2, iFixAi, Orca, Diagram Design, AI Memory.

Is My Claude Code Mods safe to run?

Deduped does not own, audit or vouch for it. Read the README and license, run it on your own systems first and review every command before you run it.