All Claude Code modsbarmoshe/bar-mods
plan-progress
Where a long build stands, beside the conversation, from a plain Markdown plan that keeps itself current: commits that name a step move it, and when the work moves past an open step it says so
review UI rewrite
plan-progress reaches L2 (writes or runs) and passed claude plugin validate on Claude Code 2.1.308.
- Events hooked: 6
- API methods referenced: 20
- Access from classified calls: L2, writes or runs: runs processes, writes files, drives Claude, writes the prompt box, reads files, reads env vars, reads mod state, persists state, draws
- Reads mod state: the scan does not record whose state, so this does not show that it reads another mod’s values
- Static scan, not a runtime test
Install hint
/plugin install plan-progress --marketplace barmoshe/bar-modsFrom the repository's own marketplace. Confirm the plugin name in the repository's README before installing. Mods need Claude Code 2.1.287 or later.
Access
L2 Writes or runsruns processes, writes files, drives Claude, writes the prompt box, reads files, reads env vars, reads mod state, persists state, drawsValidation
Passed on Claude Code 2.1.308View the source on GitHub Back to the list
What the scan recorded
- Observed events
- every prompt, every tool call
- Hooks
session.start, command.run {command=/"^(?:plan-progress:)?progress$"/}, prompt.submit, tool.call, turn.complete, ui.render {component=AbovePrompt}, ui.render {component=Pane, requestId=plan-progress}- API calls
$.clock.after, $.clock.every, $.clock.now, $.env.get, $.fs.read, $.fs.stat, $.fs.write, $.process.run, $.prompt.fill, $.session.version, $.state.get, $.state.set, $.store.delete, $.store.get, $.store.set, $.tool.register, $.ui.close, $.ui.open, $.ui.resolve, $.ui.toast- Validation on 2.1.308
- Passed
- Scanned revision
9815111bada9- Marketplace passed
- bar-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. plan-progress/hooks/lib/grammar.ts:32, plan-progress/hooks/lib/grammar.ts:197, plan-progress/hooks/lib/grammar.ts:203, plan-progress/hooks/lib/grammar.ts:204
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.
More from barmoshe/bar-mods
- mission-controlA live pane: context ring, session cost, a colored timeline of every tool call, files edited, and a sports-co…
- modsmithA workbench for building Claude Code mods: which mods loaded, a live tape of every event with its real payloa…
- rtl-kitRight-to-left for Claude Code mods: one file to copy into a mod that orders Hebrew and Arabic right on every…
- surface-probeA pane that shows what this surface does before you design for it: its width and placement, which elements it…
- turn-meterA band above the prompt: the tool running now during a turn, and a one-line summary of the last turn after it
Badge for your README
Authors can show the latest scan result in their README. Each badge links to this page.
[](https://mods.aidojo.si/mods/barmoshe--bar-mods--plan-progress/)
[](https://mods.aidojo.si/mods/barmoshe--bar-mods--plan-progress/)