rice-session-accounts

What the scan recorded

Observed events

Bash calls, compaction, subagent spawns, WebFetch calls, WebSearch calls, every prompt

Hooks

process.run, process.spawn, tool.call {tool=Bash}, ui.render {component=Pane}, ui.close {id=?}, session.start, turn.start, session.end, command.run {command=rice-account}, session.authorize, http.fetch, session.*, turn.complete, command.run {command=usage}, command.run {command=status}, model.*, session.compact, agent.spawn, tool.call {tool=WebFetch}, tool.call {tool=WebSearch}, prompt.submit, turn.step, prompt.autocomplete

API calls

$.clock.after, $.clock.now, $.clock.sleep, $.command.register, $.env.get, $.env.set, $.fs.exists, $.fs.read, $.fs.stat, $.fs.write, $.http.fetch, $.process.run, $.session.cwd, $.session.model, $.session.version, $.settings.read, $.state.get, $.state.set, $.store.delete, $.store.get, $.store.set, $.ui.close, $.ui.invalidate, $.ui.log, $.ui.open, $.ui.resolve, $.ui.status, $.ui.toast

Validation on 2.1.312

Passed

Scanned revision

af30e671ec51

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/credentials.ts:118, hooks/credentials.ts:560, hooks/credentials.ts:572, hooks/descendants.ts:61, hooks/descendants.ts:64

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.