Results for “session-logs”

Extract, score, and backlog skill idea candidates from Claude Code session logs for a weekly skill generation pipeline.

Diagnose the current OMC session or repo state using logs, traces, state, and focused reproduction

Session-end memory garbage collector. Promotes valuable L2 session facts to L1 atomic memory, wipes L2, and rotates oversized audit logs. Run at end of session to prevent context inflation and storage bloat.

Files.com API skill. Use when working with Files.com for sessions, action_logs, action_notification_exports. Covers 324 endpoints.

session-stats

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

Manage environment variables and secrets in Claude Code sessions without exposing their values to logs, diffs, or context.

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

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.

Audit historical Claude Code token usage from JSONL session files — shows total spend, cache hit rates, top costly sessions, weekly trends, and where tokens are going. Run after heavy sessions or weekly to measure optimization impact.

Analyzing session replays, extracting persona-based behavioral patterns, and storytelling UX issues. Reads the 'why' from real user operation logs. Works with Field/Echo for persona validation.

Analyze Linux system logs including auth.log, syslog, systemd journal, and auditd to reconstruct user activity, detect unauthorized access, and establish event timelines on compromised systems.

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

**Server Logs:**

Get session reports, cost breakdowns, and blocker details from Clade

Logs board meeting decisions with a two-layer memory architecture, separating raw transcripts from approved decisions, and provides commands to review past decisions and overdue action items.

Log workouts, plan routines, track progress, and get intelligent coaching for any fitness level.

Search and ask questions about coding agent session history across Claude Code, Codex, and Cursor. Use when asking what was worked on, what was tried before, how a problem was investigated across sessions, what happened recently, or any question about past agent sessions. Also use when the user references prior sessions, previous attempts, or past investigations — even without saying 'sessions' explicitly.

Report AI token usage and estimated costs. Use when: owner asks about costs today/yesterday/this week, per session, or per model. Shows main session, cron jobs, and subagents. Answers: 'how much did today cost?', 'how much was this session?', 'what was last week's spend?'

Skill for the Sessions area of paddock. 50 symbols across 13 files.

Stores verified cross-session facts, decisions, preferences, and open questions without secrets, speculation, or monitoring.

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

Maintain durable session memory across agent disconnects by writing structured checkpoints to the repo's session directory, enabling context recovery.

<!-- IJFW: narration-not-applicable -->

Records daily activities, progress, decisions, and learnings in structured chronological markdown files.

Diagnose your own behavior by reading the structured logs you leave behind — turns.jsonl, events.jsonl, chat_history.jsonl, scheduler.yaml. Use when something has gone wrong (a message didn't land, a scheduled job isn't firing, a communication pattern feels off), when you need to understand a pattern over many turns, or when cost / token usage needs auditing. Covers jq query recipes and points at the debugging-jobs / debugging-communication / debugging-drift companion guides for specific failure modes.

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.

Generates audit logs and usage reports for Google Workspace accounts via the Admin SDK Reports API.

Collect, parse, and correlate system, application, and security logs to reconstruct events and establish timelines during forensic investigations.

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