It runs inside the Claude Code process. The side panel is only what the author's README names. Read the repo before you install, or run claude plugin validate on the plugin folder.
Version
0.1.0
License
MIT
Repo stars
4
Last change
2026-10-01
What it can reach
Draws in the session
Sees tool calls
Reads this turn's file edits
New sessions load it; in an open session run /reload-plugins. Claude Code 2.1.287 or later. The evidence tool needs a local listener; where that is refused, as in a sandboxed launch, /evidence and the status line still work. The ledger starts over on a reload or a new session.
The marketplace name is claude-code-mods. The marketplace also holds mod-scout, usage-meter, and resume-nudge. This one installs on its own. The plugin's manifest names Jason Walls. The record of the checks that ran is why this page files it under workflow. test-pulse, by Singh-AP, draws pass or fail on the status line and marks flakes. test-hud, by ice-lfernandes, draws each test run with a sparkline of failures. This one keeps a ledger of real checks, tests, type-checks, builds, linters, and validators, from each Bash call's own error flag, and of the files edited after the last pass. /evidence and Claude's evidence tool say tested only when every edit has a passing check after it. It observes and never blocks a call.
Demo
Screenshot of the author's GitHub page.
What it hooks into
session.startWhen a session starts
tool.callAround a tool call, where it can hold oneBashmcp__check-ledger__evidence
command.runWhen you run its slash command/evidence
Read from the on() calls in its hook modules. Open its source under Files to check what each one does.
Slash commands 1
/evidenceWhich checks ran and which edits came after them
Files
The author's README and source, 4 files. They load when you open them.