devtools

What the scan recorded

Observed events

every tool call, classic hooks

Hooks

tool.call, tool.check, session.start, classic.SessionStart, command.run {command=devtools|devtools-status|devtools-break|devtools-list|devtools-pause|devtools-continue|devtools-disable|devtools-enable|devtools-record|devtools-export|devtools-errors|devtools-permissions|devtools-help|bp|bpl|bpn|bpc|bpe|bpp}, session.append {door=tool-result}, ui.render {component=Pane, requestId=devtools}, ui.render {component=ToolUse}, ui.render {component=ToolGroup}, ui.render {component=AbovePrompt}

API calls

$.clock.after, $.clock.now, $.command.register, $.fs.exists, $.fs.stat, $.fs.write, $.session.cwd, $.session.id, $.session.messages, $.settings.read, $.state.get, $.state.set, $.store.get, $.store.set, $.tool.check, $.ui.ask, $.ui.log, $.ui.open, $.ui.resolve, $.ui.status, $.ui.toast

Validation on 2.1.302

Passed

Scanned revision

5015f53869ef

Marketplace passed

claude-devtools-mod

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. src/core/events.ts:89, src/core/events.ts:90, src/core/events.ts:91, src/core/events.ts:92, src/core/events.ts:93, src/core/events.ts:94, src/core/events.ts:95, src/core/events.ts:96, src/core/events.ts:97, src/core/events.ts:98, src/core/events.ts:99, src/core/events.ts:100, src/core/events.ts:101, src/core/events.ts:102, src/core/events.ts:103, src/core/events.ts:104, src/core/events.ts:111, src/core/events.ts:127, src/core/events.ts:291

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.