context-inspector

What the scan recorded

Observed events

every tool call, compaction

Hooks

session.start, session.end, session.append, tool.call, turn.step, session.compact, turn.complete, command.run {command=context-inspect}, command.run {command=context-pane}, command.run {command=context-export}, ui.render {component=Pane, requestId=context-inspector}

API calls

$.clock.after, $.command.register, $.env.get, $.fs.write, $.session.id, $.session.messages, $.session.usage, $.ui.invalidate, $.ui.open, $.ui.resolve, $.ui.status, $.ui.toast

Validation on 2.1.303

Passed

Scanned revision

82f9bf698508

Marketplace passed

my-claude-code-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. context-inspector/hooks/core/analyze/rereads.ts:45, context-inspector/hooks/core/analyze/rereads.ts:54, context-inspector/hooks/core/entities.ts:39, context-inspector/hooks/core/redact.ts:12, context-inspector/hooks/core/redact.ts:19, context-inspector/hooks/core/tokens.ts:28

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.