All Claude Code modslperezmo/session-nametag
session-nametag
Names and colors each Claude Code session when it starts (folder, branch, instance number, machine, model, start time), so many sessions are easy to tell apart. /nametag picks the style.
session-nametag reaches L2 (writes or runs) and passed claude plugin validate on Claude Code 2.1.302.
- Events hooked: 5
- API methods referenced: 20
- Access from classified calls: L2, writes or runs: drives Claude, reads files, reads env vars, persists state, draws
- Static scan, not a runtime test
Install hint
/plugin install session-nametag --marketplace lperezmo/session-nametagFrom 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 runsdrives Claude, reads files, reads env vars, persists state, drawsValidation
Passed on Claude Code 2.1.302View the source on GitHub Back to the list
What the scan recorded
- Observed events
- Only what it hooks
- Hooks
session.start, turn.start, turn.complete, command.run, session.end- API calls
$.clock.after, $.clock.every, $.clock.now, $.command.register, $.command.run, $.env.get, $.fs.exists, $.fs.read, $.session.cwd, $.session.id, $.session.model, $.session.repo, $.session.root, $.session.turns, $.session.usage, $.store.delete, $.store.get, $.store.keys, $.store.set, $.ui.log- Validation on 2.1.302
- Passed
- Scanned revision
654d05f198ec- Marketplace passed
- session-nametag
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.
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/lperezmo--session-nametag--session-nametag/)
[](https://mods.aidojo.si/mods/lperezmo--session-nametag--session-nametag/)