vibe-gambit

What the scan recorded

Observed events

Only what it hooks

Hooks

session.start, command.run {command=chess}, ui.message {requestId=chess}, ui.render {component=Pane, requestId=chess}, ui.render {component=PromptHint}

API calls

$.clock.after, $.clock.every, $.clock.now, $.clock.sleep, $.command.register, $.env.get, $.fs.exists, $.fs.read, $.fs.write, $.http.fetch, $.process.run, $.process.spawn, $.session.id, $.settings.read, $.state.get, $.state.set, $.store.delete, $.store.get, $.store.set, $.ui.close, $.ui.invalidate, $.ui.open, $.ui.panes, $.ui.resolve, $.ui.status, $.ui.toast

Surface modules

hooks/board.tsx

Validation on 2.1.302

Passed

Scanned revision

be9aaacf9e9b

Marketplace passed

vibe-gambit

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. hooks/lichess.ts:156

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.