prompt-hud

What the scan recorded

Observed events

Only what it hooks

Hooks

session.start, session.measure, ui.render {component=AbovePrompt}

API calls

$.clock.every, $.clock.now, $.env.get, $.process.run, $.session.id, $.session.usage, $.state.get, $.state.set, $.ui.resolve

Validation on 2.1.302

fails on 2.1.302

Validator output

modules../register.tsx: prompt-hud.error is not declared: the manifest's types contract must name it in interface PluginState { prompt-hud: { error: ... } }; modules../register.tsx: prompt-hud.limits is not declared: the manifest's types contract must name it in interface PluginState { prompt-hud: { limits: ... } }; modules../register.tsx: prompt-hud.snap is not declared: the manifest's types contract must name it in interface PluginState { prompt-hud: { snap: ... } }; modules../register.tsx: prompt-hud.tokens is not declared: the manifest's types contract must name it in interface PluginState { prompt-hud: { tokens: ... } }; ./register.tsx hooks: session.start, session.measure, ui.render{component=AbovePrompt}; ./register.tsx calls: $.clock.every, $.clock.now, $.env.get (via scan), $.process.run (via scan), $.session.id (via scan), $.session.usage (via refreshContext, refreshUsage), $.state.get, $.state.set, $.ui.resolve; ./register.tsx env writes: nothing; ./register.tsx env reads: HOME; ./register.tsx state writes: prompt-hud.error, prompt-hud.limits, prompt-hud.snap, prompt-hud.tokens; ./register.tsx state reads: prompt-hud.error, prompt-hud.limits, prompt-hud.snap, prompt-hud.tokens

Scanned revision

81b893659719

Marketplace warnings

prompt-hud

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.