filetree-hiroshi

What the scan recorded

Observed events

classic hooks, every tool call, every prompt

Hooks

classic.SessionStart, session.start, classic.FileChanged, tool.call, prompt.submit, session.end, turn.complete, ui.focus {component=Pane, requestId=filetree-hiroshi}, ui.scroll {component=Pane, requestId=filetree-hiroshi}, ui.render {component=AbovePrompt}, command.run {command=filetree}, ui.close {id=filetree-hiroshi}, ui.render {component=Pane, requestId=filetree-hiroshi}

API calls

$.clock.after, $.clock.every, $.clock.now, $.command.register, $.env.get, $.fs.exists, $.fs.list, $.fs.read, $.fs.write, $.process.run, $.session.cwd, $.session.id, $.state.get, $.state.set, $.ui.close, $.ui.open, $.ui.panes, $.ui.resolve, $.ui.toast

Validation on 2.1.312

Passed

Scanned revision

6cfae3206f6d

Marketplace passed

hiroshi-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. filetree-hiroshi/hooks/git.ts:30, filetree-hiroshi/hooks/git.ts:54

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. What a mod can access and how the scan works.