session-logs

session-logs is a skill for Claude Code from lakpriya1s/agent-rack. It costs 19 tokens per session (455 once invoked), scanned A, original, MIT.

A command for reading the saved standard output and error events from a background coding-agent session. These are the messages and tool activity produced while it runs.

In plain words
What is it for?
Use it to inspect a session's progress, read recent events, or continue from a cursor in the event stream.
Why use it?
It gives you a detailed record of what the session has done, including newer events since your last check.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the agent-rack plugin — 11 skills shipped together

Good fit Use it to inspect a session's progress, read recent events, or continue from a cursor in the event stream.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/lakpriya1s/agent-rack/session-logs
Install

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.

Any agent
npx skills add lakpriya1s/agent-rack --skill session-logs
Clone the repo
git clone --depth 1 https://github.com/lakpriya1s/agent-rack

Made for: Claude Code.

Or install agent-rack, the plugin that ships this one along with the rest of its 11 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for session-logs

README.md
[![agentmods](https://agentmods.dev/badge/skills/lakpriya1s/agent-rack/session-logs.svg)](https://agentmods.dev/skills/lakpriya1s/agent-rack/session-logs)
Your own site
<a href="https://agentmods.dev/skills/lakpriya1s/agent-rack/session-logs"><img src="https://agentmods.dev/badge/skills/lakpriya1s/agent-rack/session-logs.svg" alt="Measured on agentmods" height="20"></a>
Per session 19 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 455 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00019 $0.00455
Opus 5 $0.00010 $0.00228
Sonnet 5 $0.00004 $0.00091
Haiku 4.5 $0.00002 $0.00046

Measured 7d ago against content hash 2d97491bdcf3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

session-logs 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 7d 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.

plugins/agent-rack/skills/session-logs/SKILL.md · 41 lines

What it actually says

Read paginated raw events from a session through agent-rack's agent_session_logs MCP tool.

Raw slash-command arguments: $ARGUMENTS

Parsing

First word is sessionId. Recognized flags: --cursor <n> (return only events at or after this cursor, default 0), --tail <n> (instead of a cursor, return only the most recent N events), --limit <n> (max events to return, default all remaining).

Execution

Call mcp__plugin_agent-rack_agent-rack__agent_session_logs with sessionId and any given cursor/tail/limit.

Output

The result is a page object, not a bare array:

  • events — the ParsedAgentEvent objects (type, content, and for tool events toolName/input/output, each with a timestamp).
  • nextCursor — pass this as --cursor on a follow-up call to fetch only what is new. Use this when watching a session over several calls instead of re-reading the whole log each time.
  • droppedCount — non-zero means older events aged out of the retained log before you read them. Say so rather than presenting the timeline as complete.
  • totalEvents / oldestCursor — the monotonic total produced, and the oldest still retained.

This is lower-level than /agent-rack:session-status — use it when the user wants the actual event-by-event stream (e.g. debugging why a session behaved a certain way), not just the final summary. Present it as a readable timeline rather than dumping raw JSON when there are more than a handful of events.

Changes

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.

  1. 7d ago First seen · 41 lines · 19 tokens per session scan A 2d97491bdcf3

Subscribe to this mod's changes

session-logs is a skill published in the GitHub repository lakpriya1s/agent-rack (1 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 455 once invoked, about $0.0001 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-31.

Related

Other skills, from other repositories

cao-workflow

Author and run CAO Python workflow scripts — multi-step, parameterized, fan-out orchestrations executed by cao workflow run. Use when the user wants a repeatable multi-step job (e.g. data analysis over many files, a review pipeline, a parameterized batch). Authoring ends at a validated script file; running it is a…

awslabs/cli-agent-orchestrator · 79 tokens

aidlc-portfolio

Coordinate multiple AI-DLC workflows across repositories and Git worktrees using an evidence-backed portfolio catalog and deterministic workspace tooling. Use when initializing an AI-DLC portfolio workspace, discovering organization or business context, registering projects and dependencies, creating child intents and…

awslabs/cli-agent-orchestrator · 74 tokens

cao-plugin

Create a new CAO (CLI Agent Orchestrator) plugin. Use this skill whenever the user wants to add a plugin that reacts to CAO lifecycle or messaging events, scaffold a plugin package, understand plugin requirements, or integrate an external system (Discord, Slack, dashboards, logging, metrics) with CAO. Also use when…

awslabs/cli-agent-orchestrator · 96 tokens

cao-provider

Create a new CLI agent provider for CAO (CLI Agent Orchestrator). Use this skill whenever the user wants to add support for a new CLI-based AI agent (e.g., a new coding assistant CLI), integrate a new provider, or scaffold a provider implementation. Also use when the user asks about the provider architecture, what…

awslabs/cli-agent-orchestrator · 81 tokens

cao-session-management

Interact with CAO (CLI Agent Orchestrator) — launch multi-agent sessions, check status, send follow-up instructions, unblock stuck terminals, or shut down sessions. Use when working with CAO sessions in any capacity.

awslabs/cli-agent-orchestrator · 49 tokens

agui-author

Author live dashboard UI from an agent via the emitui MCP tool. Emit one of six allow-listed components (approvalcard, choiceprompt, diffsummary, progress, metric, agentcard) with JSON props and it renders in any AG-UI client watching the fleet. Use when you want the operator to see a decision, a diff, or a status…

awslabs/cli-agent-orchestrator · 93 tokens