slime-dashboard

What the scan recorded

Footprint

Unavailable or incomplete. Recorded events and calls below may omit access.

Observed events

compaction, subagent spawns, ? calls, every tool call, classic hooks

Hooks

session.start, command.run {command=slime-dashboard}, command.run {command=effort}, command.run {command=compact}, session.compact, turn.start, agent.offer, agent.spawn, turn.step, tool.call {tool=?}, tool.call, classic.UserPromptSubmit, classic.Notification, turn.complete, session.measure, ui.render {component=Pane, requestId=slime-dashboard}, ui.render {component=Pane, requestId=dungeon}

API calls

$.agent.list, $.agent.spawn, $.clock.after, $.clock.every, $.clock.now, $.command.register, $.command.run, $.env.get, $.fs.list, $.fs.read, $.fs.write, $.http.fetch, $.model.fork, $.process.run, $.prompt.submit, $.session.cwd, $.session.id, $.session.messages, $.session.model, $.session.send, $.session.usage, $.state.get, $.state.set, $.store.get

Validation on 2.1.302

fails on 2.1.302

Validator output

types: line 1: `import` reaches outside the file; the contract must be self-contained (no import, export … from, require or reference)

Scanned revision

10a293833a7d

Marketplace failed

slime-dashboard: plugins[0] plugin.json → types: line 1: `import` reaches outside the file; the contract must be self-contained (no import, export … from, require or reference)

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.