why-log

why-log is a Claude Code mod by Plagemes that records why each file was changed; /why shows the reasoning behind any file's edits.

Updated 2026-10-15

What is why-log?

why-log is a Claude Code mod by Plagemes that records why each file was changed; /why shows the reasoning behind any file's edits. It is listed under Interface and has 1 GitHub stars.

TypeClaude code mod
AuthorPlagemes
RepositoryPlagemes/claude-mods
Popularity1 GitHub stars
CategoryInterface
SecurityLow risk (96/100)
Rank#2,255 of 5,272 Claude Code mods; #950 in Interface
LicenseMIT
Last commit2026-10-15
Hooks6 events
SeesEdit|Write|NotebookEdit calls
Draws onnothing

Is why-log safe to install?

why-log scores 96/100 on the MCPMods security check: Low risk. No checks raised a concern. It passed 7 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
Drives Claude (model calls, prompts)Note
Passes claude plugin validatePass
Has an open-source licensePass

API calls in its code

CallWhat it means
$.clock.after
$.clock.now
$.command.register
$.model.completedrives Claude
$.session.root
$.store.getkeeps its own state
$.store.setkeeps its own state
$.ui.logdraws interface

How do I install why-log?

  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/Plagemes/claude-mods
    claude plugin validate ./claude-mods/mods/why-log
  3. Install it. Run this in your terminal, then /reload-plugins in an open session.
    claude plugin marketplace add Plagemes/claude-mods && claude plugin install why-log@claude-mods

Or ask Claude to set it up

Paste this into Claude Code and it installs why-log for you:

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

More from Plagemes/claude-mods

This repository has at least 9 Claude Code mods on MCPMods.

  • a11y-guard: Flags accessibility misses as Claude writes UI: images without alt, unlabeled buttons, clickable divs. (Low risk)
  • achievements: Unlock achievements as you work: first commit, 100 green test runs, a week-long streak and more. (Low risk)
  • activity-heatmap: A heat map of when you use Claude Code, by hour and weekday. (Low risk)
  • agent-presets: Ready-made subagents for focused jobs: debugger, test writer, doc writer and migrator. (Low risk)
  • audit-trail: Writes every action Claude takes to an append-only JSONL audit log. (Review before installing)
  • auto-checkpoint: Snapshots your work tree before every editing turn and lets you /rollback to any checkpoint. (Low risk)
  • auto-format: Formats every file Claude edits with the right formatter for its language. (Low risk)
  • autopilot: Give it a goal and success criteria; it plans, delegates, verifies and retries until the criteria pass or it needs you. (High risk)