longpi

What the scan recorded

Observed events

every prompt, /"^mcp__longpi__"/ calls

Hooks

session.start, prompt.compose, prompt.submit, turn.start, turn.complete, ui.render {component=AbovePrompt}, ui.render {component=ToolUse, props has {tool=/"^mcp__longpi__"/}, ui.render {component=ToolResult, props has {tool=/"^mcp__longpi__"/}, tool.call {tool=/"^mcp__longpi__"/}, command.run {command=longpi}, ui.render {component=Pane, requestId=longpi}

API calls

$.clock.after, $.clock.every, $.clock.now, $.clock.sleep, $.command.register, $.env.get, $.fs.list, $.fs.read, $.fs.stat, $.fs.write, $.http.fetch, $.model.complete, $.process.run, $.prompt.fill, $.prompt.submit, $.session.append, $.session.id, $.state.get, $.state.set, $.store.get, $.store.set, $.tool.register, $.ui.ask, $.ui.blit, $.ui.close, $.ui.copy, $.ui.log, $.ui.open, $.ui.resolve, $.ui.status, $.ui.toast

Validation on 2.1.302

Passed

Scanned revision

9df766acc9ab

Marketplace passed

longpi-mod

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/core/calendar.ts:39, hooks/core/calendar.ts:133, hooks/core/core/llm-call.ts:91, hooks/core/datain/tools.ts:31, hooks/core/indicators.ts:640, hooks/core/method-collect.ts:69, hooks/core/privacy/export.ts:143, hooks/core/records.ts:96, hooks/core/runner.ts:178, hooks/core/stores/limits.ts:16, hooks/core/tracking.ts:176

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.