Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add rules/alphabitcore/nexus-gateway/session-handoffgit clone --depth 1 https://github.com/AlphaBitCore/nexus-gatewayWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00775 | $0.00775 |
| Opus 5 | $0.00387 | $0.00387 |
| Sonnet 5 | $0.00155 | $0.00155 |
| Haiku 4.5 | $0.00077 | $0.00077 |
Grade A, and why
session-handoff scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session handoff at context-full
Canonical text lives in
CLAUDE.mdunder Mandatory rules. This rule is the IDE-side surfacing; when this file disagrees withCLAUDE.md,CLAUDE.mdwins.
When to trigger
Proactively offer the handoff workflow when any of these apply:
- The conversation is approaching the auto-compact threshold (the assistant senses long context, ~150k+ tokens, or the IDE / harness signals "context full").
- A multi-phase program is closing out (e.g., the OSS-readiness review's Phase 4 capstone).
- Tool-call turn count is high (>~50 turns of accumulated state).
- A major
git pushjust landed work the next session needs to build on.
What the handoff document contains
Typical location: docs/handoffs/program-name.md for repo-tracked plans, or <program-area>/HANDOFF.md for area-local plans, or /tmp/<program>-handoff.md for local-only (less reliable).
Required sections (mirror the canonical example):
- Mission — program goal + current phase.
- Architecture model — load-bearing facts the next session needs to design / debug against without re-reading the whole codebase. Keep dense (tables ok).
- API / surface inventory — what the program operates on.
- Work units catalog — concrete units the next session executes (scenarios, modules, tasks).
- Existing infrastructure — what to build on, what to avoid rewriting.
- Binding rules — pointers into CLAUDE.md + memory anchors the next session must load.
- Recent changes affecting the work — renames, deletions, contract changes since the program plan was first drafted.
- Suggested program structure — phases + first concrete steps.
- Repo state snapshot — branch / tip commit / known dirty WIP from parallel sessions.
Why on-disk, not just memory
- Maintainer-local memory persists across sessions but is one-line indexed; can't carry a 300-line architecture map.
- Auto-compact summarizes the conversation but loses fidelity on specifics (file paths, struct fields, contract details).
- An on-disk handoff document is the single source of truth the next session reads. Memory anchor + on-disk plan together = full handoff.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 57 lines · 775 tokens per session scan A 963b7b40be90
session-handoff is a cursor rule published in the GitHub repository AlphaBitCore/nexus-gateway (22 stars, last pushed 7d ago), licensed Apache-2.0. It adds 775 tokens to every session, about $0.0039 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other cursor rules, from other repositories
10-deterministic-audit
Enforce deterministic audit behavior — no invented controls, cite authoritative sources, emit traceable artifacts.
flagship_author
How to author a flagship in ks-cookbook.
recipe_author
How to author a recipe in ks-cookbook.
30-framework-routing
Route tasks to HIPAA, HITECH, PCI-DSS, SOC 2, ISO 27001, NIST CSF, NIST AI RMF, FERPA, COPPA, CCPA, US state privacy, GDPR, FedRAMP, SOX, CMMC, and GLBA skills based on user intent and presets.
00-compliance-agent-core
Core compliance agent mission, PHI redaction gate, and audit lifecycle for HIPAA, PCI-DSS, and SOC 2.
20-phi-redaction-first
PHI redaction first — Presidio gate, token handling, and minimum necessary LLM access for HIPAA workflows.