All Claude Code modsdougcunha/claude-mods
session-cleanup
The /cleanup command lists the temporary files the session created and the Git items it left (uncommitted changes, changed submodules, a detached HEAD, unpushed commits); choose what to send to the trash and what to ask Claude to fix.
review UI rewrite
session-cleanup reaches L2 (writes or runs) and passed claude plugin validate.
- Events hooked: 6
- API methods referenced: 18
- Access from classified calls: L2, writes or runs: runs processes, writes files, drives Claude, reads files, reads env vars, reads mod 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 session-cleanup --marketplace dougcunha/claude-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, reads files, reads env vars, reads mod state, drawsValidation
PassedView the source on GitHub Back to the list
What the scan recorded
- Observed events
- Bash calls, PowerShell calls
- Hooks
session.start, tool.call {tool=Bash}, tool.call {tool=PowerShell}, turn.complete, session.end, command.run {command=?}, ui.render {component=Pane, requestId=session-cleanup}- API calls
$.clock.now, $.command.register, $.env.get, $.fs.exists, $.fs.list, $.fs.stat, $.fs.write, $.process.run, $.prompt.submit, $.session.cwd, $.session.id, $.session.root, $.state.get, $.state.set, $.ui.close, $.ui.open, $.ui.resolve, $.ui.toast- Validation
- Passed
- Scanned revision
78689f025eab- Marketplace passed
- claude-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. session-cleanup/hooks/git.ts:33, session-cleanup/hooks/scan.ts:115, session-cleanup/hooks/shell.ts:51
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 dougcunha/claude-mods
- feature-progressA tool any spec-driven flow calls to report the progress of a feature and its tasks; a band above the prompt…
- session-infoSession pane: context, cost and turns, the prompt cache with the time until it expires, keep warm and a guard…
- topic-guardBefore a prompt enters the session, a small model judges whether it belongs to the session's topic. When it s…
- visual-reviewThe /visual-review command shows the design of the changes against a base branch as a diagram in the browser:…
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/dougcunha--claude-mods--session-cleanup/)
[](https://mods.aidojo.si/mods/dougcunha--claude-mods--session-cleanup/)