Results for “session-baton”

At the start of a session, reads the session baton file to restate the goal and next task, and opens any doc listed under "Read first" before confirming the next step with the user.

Manages conversation context across sessions and compactions using TLDR summaries, structured documentation, and searchable history.

Creates comprehensive handoff documents for seamless AI agent session transfers. Triggered when: (1) user requests handoff/memory/context save, (2) context window approaches capacity, (3) major task milestone completed, (4) work session ending, (5) user says 'save state', 'create handoff', 'I need to pause', 'context is getting full', (6) resuming work with 'load handoff', 'resume from', 'continue where we left off'. Proactively suggests handoffs after substantial work (multiple file edits, complex debugging, architecture decisions). Solves long-running agent context exhaustion by enabling fresh agents to continue with zero ambiguity.

Start-of-session routine — load context, check state, suggest next task. Use at the beginning of a fresh session or after a context reset.

Compact the current session into a single detailed handoff message that can be pasted into a fresh agent run. Use when switching context, ending a session, or avoiding context-window loss.

Diagnose and fix automatic batching regressions in React 18 class components with a decision tree for setState behavior changes.

Optimizes long-running agent sessions with structured context compression, summarization, and durable handoff summaries that preserve decisions, files, risks, and next actions.

Generate a project-level context snapshot for resuming work in a fresh session

End-of-session context handoff. Saves session state so the next session or a parallel agent can pick up exactly where the left off. Run this when context is getting full (~80%) or before stopping work.

Detect and exploit session fixation (WSTG-SESS-01, WSTG-SESS-03) and session exposure (WSTG-SESS-04) by testing whether the server issues a new session token post-authentication, whether pre-login tokens remain valid after login, and whether session IDs are transmitted over HTTP or included in GET parameters. Analyze token randomness via Burp Sequencer. Test JSESSIONID, ASP.NET Forms Auth cookies. Tools: OWASP ZAP, Burp Suite Repeater/Sequencer, JHijack.

session-stats

セッション再開時に最新5件のhandoffを読み込み文脈を復元するスキル。「おはよう」「こんにちは」「こんばんは」「再開」「restart」または /resume-session を呼んだ時にトリガーする。new-session の対（読込側）。

Session handoff generation and loading. Trigger: session end, context full, /handoff

Capture delivery evidence, commands, changed files, blockers, and standards feedback after a work session.

Show DAG state, agent progress, and branch status for an AgentHub session.

Display DAG state, agent progress, and branch status for an AgentHub session.

Search locally saved Codex session history stored in SQLite and session_index.jsonl, with filters for provider, time range, and archived status.

Keeps long AI sessions on track by tracking decisions, detecting scope creep, and flagging drift before it costs work.

Maintains a persistent session memory across Claude sessions by loading project state at startup, capturing errors and decisions during work, and writing structured handoff summaries at session end.

Fetch meetings, transcripts, summaries, and action items from Fathom API. Use when user asks to get Fathom recordings, sync meeting transcripts, or fetch recent calls.

Run multi-agent research discourse session. Use when the user requests to "start a research party" or "run a journal club".

Quickly refreshes project state when resuming work by reporting git status, recent commits, environment, memory staleness, pending tasks, and red flags.

Compacts the current conversation into a handoff document for another agent to pick up, referencing existing artifacts by path or URL instead of duplicating them.

Search claude-mem's persistent cross-session memory database. Use when user asks "did we already solve this?", "how did we do X last time?", or needs work from previous sessions.

Manage and compress conversation context in long sessions. Detect when context is growing large, summarize completed work phases, archive old findings while preserving key decisions. Prevents context degradation.

Compact the current conversation into a handoff document for another agent to pick up. Save to a user-configured location (OS temp, home folder, or per-project .handoff/), redact secrets before write, suggest skills for the next session, and auto-load the latest handoff on the next SessionStart. First-run setup asks where to save so the project folder never gets cluttered. Use when the user says 'hand this off', 'handoff doc', 'summarize this for a new session', 'compact this conversation', 'I'm ending this session', 'pick this up later', or any variation signaling intent to pass work to a fresh agent. Also trigger on implicit signals: the user announcing they're switching machines, ending the day mid-task, or context is growing long without a natural stopping point.

Search and analyze your own session logs (older/parent conversations) using jq.

建议在逻辑间隔处手动压缩上下文，以在任务阶段中保留上下文，而非任意的自动压缩。

Boot the session, load context from the vault, and surface what matters

Request a re-anchoring block: your goal, standing constraints, budget, and the actions you already completed this session. Call this whenever you feel uncertain about what you were doing, suspect you lost context, or before any consequential action.

Generates a copy-paste handoff prompt for starting a new session by collecting current session context, project files, and git state.

Batch visual production workflow for campaigns. Accepts a content calendar or campaign brief, produces multiple platform-ready assets with organized bundle output and machine-readable manifest. Trigger for 'batch design', 'content calendar to assets', 'campaign batch', 'produce all campaign visuals', or 'bulk asset generation'.

Write an end-of-session handover LogEntry capturing current state, open threads, next action, and git context for session continuity.

Commit the session to durable vault memory and prepare a clean resume point

Multiple AI agent sessions working on the same repository cause chaos. Session A is on branch feature/auth. Session B switches to main to check something. Session A's next tool call fails because the branch disappeared. Or worse: Session B force-pushes over Session A's work.