read-aloud

What the scan recorded

Observed events

every prompt

Hooks

session.start, turn.complete, prompt.submit, ui.render {component=AbovePrompt}, command.run {command=speak}

API calls

$.clock.every, $.clock.now, $.command.register, $.fs.read, $.fs.write, $.process.run, $.state.get, $.state.set, $.store.get, $.store.set, $.ui.log, $.ui.resolve

Validation on 2.1.304

fails on 2.1.304

Validator output

modules../register.tsx: read-aloud.hasReply is not declared: the manifest's types contract must name it in interface PluginState { read-aloud: { hasReply: ... } }; modules../register.tsx: read-aloud.speed is not declared: the manifest's types contract must name it in interface PluginState { read-aloud: { speed: ... } }; ./register.tsx hooks: session.start, turn.complete, prompt.submit, ui.render{component=AbovePrompt}, command.run{command=speak}; ./register.tsx answers its own command: command.run{command=speak}; ./register.tsx gating hook with .catch: prompt.submit; ./register.tsx calls: $.clock.every (via watchStatus), $.clock.now (via speak, watchStatus), $.command.register, $.fs.read (via watchStatus), $.fs.write (via setSpeed, speak, stopSpeaking), $.process.run (via speak, stopSpeaking), $.state.get, $.state.set, $.store.get (via getSpeed, isEnabled, speak), $.store.set, $.ui.log, $.ui.resolve; ./register.tsx state writes: read-aloud.hasReply, read-aloud.speed, read-aloud.status; ./register.tsx state reads: read-aloud.hasReply, read-aloud.speed, read-aloud.status

Scanned revision

b536a77d55ce

Marketplace passed

read-aloud

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.