claudemods

All Claude Code modshymleong/claude-mods

workbench

A Claude Code mod in hymleong/claude-mods

A side pane with Git review, real PowerShell terminals and a live monitor of the servers running on localhost. Nothing else to install.

review UI rewrite

workbench reaches L3 (network) by its classified calls and passed claude plugin validate on Claude Code 2.1.302.

Install hint

/plugin install workbench --marketplace hymleong/claude-mods

From the repository's own marketplace. Confirm the plugin name in the repository's README before installing. Mods need Claude Code 2.1.287 or later.

Access

L3 Uses the networkother: $.process.spawn, other: $.state.get, other: $.state.set, network, runs processes, writes files, drives Claude, writes the prompt box, reads files, reads env vars, persists state, draws

Validation

Passed on Claude Code 2.1.302

View the source on GitHub Back to the list

What the scan recorded

Observed events
mcp__workbench__dev_reload calls, every tool call, compaction
Hooks
session.start, tool.call {tool=mcp__workbench__dev_reload}, turn.start, turn.step, tool.call, tool.check, session.compact, turn.complete, session.end, command.run {command=workbench}, ui.close {id=workbench}, ui.focus {requestId=workbench}, ui.press {requestId=workbench}, ui.message, ui.render {component=Pane, requestId=workbench}, ui.render {component=AbovePrompt}
API calls
$.clock.after, $.clock.every, $.command.register, $.config.list, $.env.get, $.fs.exists, $.fs.list, $.fs.read, $.fs.stat, $.fs.write, $.http.fetch, $.process.run, $.process.spawn, $.prompt.fill, $.session.cwd, $.state.get, $.state.set, $.store.delete, $.store.get, $.store.set, $.tool.register, $.ui.copy, $.ui.invalidate, $.ui.open, $.ui.panes, $.ui.resolve, $.ui.toast
Surface modules
hooks/editor.tsx, hooks/terminal-input.tsx
Validation on 2.1.302
Passed
Scanned revision
e3fb8c31dc64
Marketplace warnings
claude-mods
UI rewrite review
UI hook source contains control-character strings. Review any values passed to next() as rewritten props.text; the scanner does not trace whether these strings reach that call. plugins/workbench/hooks/git.ts:17, plugins/workbench/hooks/git.ts:125, plugins/workbench/hooks/register.tsx:1213, plugins/workbench/hooks/register.tsx:1272, plugins/workbench/hooks/shell-host.ts:22, plugins/workbench/hooks/stream.ts:7, plugins/workbench/hooks/stream.ts:85, plugins/workbench/hooks/stream.ts:86, plugins/workbench/hooks/stream.ts:88, plugins/workbench/hooks/stream.ts:120, plugins/workbench/hooks/stream.ts:121

These are the hooks and API calls reported by claude plugin validate. Access levels describe the widest reach of those calls and are not safety ratings. Validation is a static check, not a runtime test, and a passing result does not prove that a mod works or is safe. How the scan works.

More from hymleong/claude-mods

Badge for your README

Reach badge for workbench Validation badge for workbench

Authors can show the latest scan result in their README. Each badge links to this page.

[![reach](https://raw.githubusercontent.com/karanb192/awesome-claude-code-mods/main/badges/hymleong--claude-mods--workbench-reach.svg)](https://mods.aidojo.si/mods/hymleong--claude-mods--workbench/)
[![validates](https://raw.githubusercontent.com/karanb192/awesome-claude-code-mods/main/badges/hymleong--claude-mods--workbench-validates.svg)](https://mods.aidojo.si/mods/hymleong--claude-mods--workbench/)