my-mod

my-mod is a Claude Code mod by vynnlee that one sentence: what the mod does and how you use it.

Updated 2026-10-07

What is my-mod?

my-mod is a Claude Code mod by vynnlee that one sentence: what the mod does and how you use it. It is listed under Interface and has 2 GitHub stars.

TypeClaude code mod
Authorvynnlee
Repositoryvynnlee/mods
Popularity2 GitHub stars
CategoryInterface
SecurityLow risk (100/100)
Rank#1,426 of 5,272 Claude Code mods; #563 in Interface
LicenseMIT
Last commit2026-10-07
Hooks2 events
Seesonly the events it hooks
Draws onnothing

Is my-mod safe to install?

my-mod scores 100/100 on the MCPMods security check: Low risk. No checks raised a concern. It passed 8 of 8 checks.

Mod footprints come from claude plugin validate, which lists every event a mod hooks and every API call it makes without running it.

CheckResult
No network accessPass
Starts no processesPass
Writes no files or configPass
Doesn't read environment variablesPass
Only sees the events it hooksPass
Doesn't drive ClaudePass
Passes claude plugin validatePass
Has an open-source licensePass

API calls in its code

CallWhat it means
$.command.register
$.state.get
$.state.set

How do I install my-mod?

  1. Check your Claude Code version. Mods need Claude Code 2.1.287 or later and are on by default.
    claude --version
  2. Read its footprint. This lists every event it hooks and every API call it makes, without running it.
    git clone https://github.com/vynnlee/mods
    claude plugin validate ./mods/.template
  3. Install it. Run this in your terminal, then /reload-plugins in an open session.
    git clone https://github.com/vynnlee/mods && claude --plugin-dir ./mods/.template

Or ask Claude to set it up

Paste this into Claude Code and it installs my-mod for you:

Install the "my-mod" Claude Code mod from https://github.com/vynnlee/mods/tree/main/.template. Run claude plugin validate on it first and show me what it can access before you enable it.

More from vynnlee/mods

This repository has 2 Claude Code mods on MCPMods.

  • prompt-drafts: Keep prompts aside as drafts of the session. End a prompt with ;; to save it instead of sending it, then /drafts to put (Low risk)