All Claude Code modsconnectwithub/loopkeeper
lk-handoff-guard
Never lose a session to the context limit: it watches context fill, writes a handoff into .claude/brain/ in time, then clears and resumes from it.
lk-handoff-guard reaches L2 (writes or runs) and passed claude plugin validate on Claude Code 2.1.312.
- Events hooked: 10
- API methods referenced: 26
- Access from classified calls: L2, writes or runs: runs processes, writes files, drives Claude, reads files, reads env vars, reads the transcript, 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 lk-handoff-guard --marketplace connectwithub/loopkeeperFrom 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 the transcript, reads mod state, persists state, drawsValidation
Passed on Claude Code 2.1.312Listed under Context and usage meters for Claude Code.
View the source on GitHub Back to the list
What the scan recorded
- Observed events
- classic hooks, every prompt, every tool call, compaction
- Hooks
session.start, classic.SessionStart, prompt.submit, turn.start, turn.step, turn.complete, tool.call, session.compact, command.run {command=handoff}, ui.render {component=AbovePrompt}, ui.render {component=Pane, requestId=handoff-guard}- API calls
$.clock.after, $.clock.now, $.command.register, $.command.run, $.env.get, $.fs.exists, $.fs.read, $.fs.write, $.model.complete, $.model.fork, $.process.run, $.prompt.submit, $.session.cwd, $.session.id, $.session.messages, $.session.usage, $.state.get, $.state.set, $.store.delete, $.store.get, $.store.set, $.ui.ask, $.ui.close, $.ui.open, $.ui.resolve, $.ui.toast- Validation on 2.1.312
- Passed
- Scanned revision
ff413ab21be1- Marketplace passed
- loopkeeper
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 connectwithub/loopkeeper
- lk-agent-mapSee and cap your subagents: cards with cost, tokens, context and progress, spawn caps with an override you ap…
- lk-attentionLook away while Claude works: a GNOME notification, a sound, a toast and a band when it needs you or finishes…
- lk-pr-watchKnow when CI breaks without leaving the session: PR and check state above the prompt, a /pr pane, toasts on c…
- lk-secret-guardA seatbelt for secrets: stops credential-shaped strings and your private deny-list of words before Claude wri…
- lk-token-budgetStop runaway token spend: budgets per session and per subagent with warn, deny-agents or stop actions, plus a…
- lk-where-am-iKnow where the session is at a glance: repo, branch, worktree, uncommitted and unpushed work, usage windows a…
- loopkeeperKeep Claude Code on a plan: stages, approval gates and a plan-scoped file budget enforced by hooks, plus mode…
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/connectwithub--loopkeeper--lk-handoff-guard/)
[](https://mods.aidojo.si/mods/connectwithub--loopkeeper--lk-handoff-guard/)