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 skills add lakpriya1s/agent-rack --skill session-logsgit clone --depth 1 https://github.com/lakpriya1s/agent-rackWrote 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.
[](https://agentmods.dev/skills/lakpriya1s/agent-rack/session-logs)<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>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.
| Model | Per session | Once 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 |
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.
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— theParsedAgentEventobjects (type,content, and for tool eventstoolName/input/output, each with atimestamp).nextCursor— pass this as--cursoron 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.
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.
- 7d ago First seen · 41 lines · 19 tokens per session scan A 2d97491bdcf3
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.
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…
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…
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…
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…
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.
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…