mefisto-planner-board

What the scan recorded

Observed events

every prompt, every tool call, Bash calls

Hooks

session.start, prompt.submit, tool.call, tool.call {tool=Bash}, turn.complete, command.run {command=mefisto-planner-board}, ui.press, ui.render {component=AbovePrompt}

API calls

$.clock.after, $.clock.every, $.command.register, $.env.get, $.process.run, $.prompt.fill, $.prompt.submit, $.session.cwd, $.session.id, $.state.get, $.state.set, $.ui.log, $.ui.resolve, $.ui.toast

Validation on 2.1.302

Passed

Scanned revision

16e791cc7c2b

Marketplace warnings

mefisto-mods

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. .claude/mods/mefisto-planner-board/hooks/logic.ts:121, .claude/mods/mefisto-planner-board/hooks/logic.ts:131, .claude/mods/mefisto-planner-board/hooks/logic.ts:135, .claude/mods/mefisto-planner-board/hooks/logic.ts:140, .claude/mods/mefisto-planner-board/hooks/logic.ts:146, .claude/mods/mefisto-planner-board/hooks/logic.ts:175

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.