my-claude-code-mods README

The project's README from github.com/YeonwooSung/my-claude-code-mods. As one markdown file: README.md.

My Claude Code Mods

Claude Code Mods Overview Create Claude Code Mods

Mods

Development

Use Node 22.19.0 or later. Dependencies are pinned in package-lock.json.

npm ci --ignore-scripts
npm test                  # core logic, no Claude Code installation/account required
CLAUDE_BIN=/path/to/claude npm run test:adapters  # full engine suites, including adapters
npm run typecheck         # requires engine-generated declarations in each .claude-plugin/types

npm test maps the core tests' claude-code/testing import to Node's test runner and Jest's expect; it does not emulate engine events. Files run sequentially so the existing performance assertions do not compete with other test processes. CI runs this independent core suite. Engine type declarations are generated locally and remain untracked; use the declarations belonging to the engine under test. See each mod's development instructions for generation/setup.

Validation target Compatibility
Node core tests Node 22.19.0; TypeScript transformation flag required
Original three engine test suites Verified with Claude Code 2.1.292
Pin Memo engine suite Verified with Claude Code 2.1.292; render trees and Button presses on terminal/Desktop
Loop Detective engine suite Verified with Claude Code 2.1.280; TypeScript checks use local 2.1.292 declarations
Model Effort Band engine suite Verified with Claude Code 2.1.292; terminal/Desktop render trees, live pixels unverified
Token Run engine suite Verified with Claude Code 2.1.292; terminal/Desktop Client keys, buttons and frame clock, live pixels unverified
Early-access Claude Code 2.1.280 Profiler works; Context Inspector lacks session.append, and Time Machine's per-test options are ignored
Live terminal/desktop UI and simultaneous mods Requires a separate interactive integration run; unit suites do not establish UI compatibility

Installation uses plugin@marketplace as described in the official Mods documentation. Add this marketplace once, then install the desired mod using its README.

For a controlled overhead comparison, use a disposable representative large repository at one fixed commit and the same Claude engine/model/permission settings. Run the same workload under four configurations: no mods, profiler only, Time Machine only, and all three. Load mods explicitly with --plugin-dir while other installed plugins are disabled; reset files and recorder stores outside the timed interval. Use a warm-up and at least five measured repetitions per configuration, alternate run order, and record wall time, tool-call count, model tokens and snapshot average. Include no-change mutating calls and actual edits. Report median/p95 and separate model latency from snapshot/hook time. The existing 20k-span/item tests bound analysis cost but do not measure combined engine overhead; no four-mode performance result is claimed here.

my-claude-code-mods (YeonwooSung/my-claude-code-mods)

Searching Database…

906 ·GitHub
My-claude-code-mods
What is this?A personal collection of custom 'mods' (plugins) for Claude Code that add things like performance profiling, context-waste analysis, a branching edit timeline with snapshots, repeated-failure detection, pinned memos, a model-effort indicator, and a small terminal game, built by YeonwooSung.
Is this one tool or a bundle of separate plugins?It is a bundle of seven independent Claude Code plugins (mods), each with its own name, README and install step, grouped together in one marketplace repo.
How do I install a mod?Add this repository as a marketplace once, then install whichever mod you want using its own README via the plugin@marketplace mechanism described in Claude Code's official Mods documentation.
Do I need a specific Node or Claude Code version?Yes — development and tests require Node 22.19.0 or later, and each mod's engine suite is verified against a specific Claude Code build, mostly 2.1.292 (Loop Detective's engine suite uses 2.1.280).
Are all the mods fully verified and stable?Not entirely: on early-access Claude Code 2.1.280 the Context Inspector lacks session.append and Time Machine's per-test options are ignored, live-pixel rendering for Model Effort Band and Token Run is unverified, and combined multi-mod performance in a real terminal/desktop session is not established by the unit suites.
What exactly does agent-profiler measure?It shows where a Claude Code session's time goes — model wait, tool calls, subagents, re-reads — and exports OTLP traces viewable in Jaeger or Tempo.
What can time-machine do with my edits?It records every tool call on a branching timeline with shadow-git snapshots so you can view files as they were at any step, explain which edit broke a test, restore, branch, compare runs, and re-run steps.
Why are several mods documented in Korean?Context Inspector, Time Machine, Loop Detective, Pin Memo, Model Effort Band and Token Run are documented in Korean (한국어), reflecting the author's own working language for those mods.
Is token-run a real productivity feature?It is a lighthearted, fully local ASCII mini-game that fills the dead time during request failures or short breaks, with jump controls and a saved best score.
What are similar projects?claude-code, gitagent, oh-dsh, memray, claude-devtools, pi-shadow-mind, yazi, kimi-code
Which topics is it in?session, context-window, jest, korean, tracing, opentelemetry, marketplace, claude-code-plugin, debugging, plugin-system, tui, observability
Creator
YeonwooSung
Size
0.5 MB
Stars
906
Updated
CommitOct 13
Age
8d
Commits · 90 Days