cells

What the scan recorded

Observed events

mcp__cells__run_cell calls, subagent spawns, every prompt, every tool call

Hooks

tool.call {tool=mcp__cells__run_cell}, session.start, prompt.compose, prompt.attachment {type=auto_mode}, agent.spawn, turn.start, turn.step, prompt.submit, tool.call {tool=mcp__cells__run_cell}, tool.call, ui.render {component=ToolUse, props has {tool=mcp__cells__run_cell}}, ui.render {component=ToolResult, props has {tool=mcp__cells__run_cell}}

API calls

$.clock.after, $.clock.every, $.clock.now, $.clock.sleep, $.fs.read, $.fs.stat, $.fs.write, $.process.run, $.process.spawn, $.prompt.submit, $.session.cwd, $.session.id, $.state.get, $.state.set, $.tool.call, $.tool.register, $.ui.invalidate, $.ui.log, $.ui.resolve

Validation on 2.1.312

Passed

Scanned revision

0b9097a7b7cc

Marketplace passed

claude-modpack

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. cells/hooks/bridge.ts:47

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.