log-rotation

log-rotation is a skill for Claude Code, Codex from jasonkneen/lazar. It costs 0 tokens per session (964 once invoked), scanned A, original, MIT.

A helper for adding navigation details to summaries of rotated Lazar session logs. Log rotation means moving an old log aside when it grows too large so a new live log can continue.

In plain words
What is it for?
Use it after a log archive is rotated or when asked to summarize the last session. It is intended to run once per archive, not on every prompt.
Why use it?
The kernel's automatic summary is minimal, so this adds useful details such as frequent prompts, commands, and files touched. It avoids changing the kernel-owned log archive.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: positional $N argument.

Good fit Use it after a log archive is rotated or when asked to summarize the last session. It is intended to run once per archive, not on every prompt.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jasonkneen/lazar/log-rotation
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 jasonkneen/lazar --skill log-rotation
Clone the repo
git clone --depth 1 https://github.com/jasonkneen/lazar

Made for: Claude Code, Codex.

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 log-rotation

README.md
[![agentmods](https://agentmods.dev/badge/skills/jasonkneen/lazar/log-rotation/github.svg)](https://agentmods.dev/skills/jasonkneen/lazar/log-rotation)
Your own site
<a href="https://agentmods.dev/skills/jasonkneen/lazar/log-rotation"><img src="https://agentmods.dev/badge/skills/jasonkneen/lazar/log-rotation/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for log-rotation

Your own site · 80×15
<a href="https://agentmods.dev/skills/jasonkneen/lazar/log-rotation"><img src="https://agentmods.dev/badge/skills/jasonkneen/lazar/log-rotation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 964 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.00000 $0.00964
Opus 5 $0.00000 $0.00482
Sonnet 5 $0.00000 $0.00193
Haiku 4.5 $0.00000 $0.00096

Measured 10d ago against content hash 617751ac2ca9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

log-rotation 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 10d 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.

src/seed-skills/_meta/log-rotation/SKILL.md · 81 lines

How it starts

The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.

log-rotation

Add a richer memory summary for a rotated Lazar stream archive.

The kernel auto-rotates stream.jsonl when it exceeds LAZAR_LOG_MAX_BYTES (default 10MB). That is the safety floor. The kernel owns logs/: sandboxed tools and hooks may read logs, but must not write, compress, prune, or repair them.

The kernel writes a minimal summary into memory/log-summaries/<ts>.md whenever it rotates. This skill is the polish layer on top: read one archive with bounded commands and append useful human navigation details to memory.

When to use

  • After kernel auto-rotation, if you want richer summaries than the minimal kernel header.
  • When a memory/log-summaries/<ts>.md file exists but needs top prompts, top commands, or a small file-touch index.
  • The user explicitly asks "summarize the last session" or similar.

Do NOT run this on every prompt. Once per archive is plenty.

Hard rules

  • logs/ is trusted kernel-owned state. Do not mv, gzip, rm, truncate, or write anything under $LAZAR_HOME/logs from a sandboxed skill or hook.
  • Rotation itself is kernel-owned and non-destructive at the moment it happens: the live log moves to .bak, and the next append creates a fresh stream.jsonl.
  • Full-fidelity archive retention is kernel policy, controlled by LAZAR_LOG_ARCHIVE_KEEP. Summaries in memory/log-summaries/ are the durable navigation layer.
  • Write enriched summaries only under $LAZAR_MEMORY, usually memory/log-summaries/ or memory/distilled/.
  • Always bound archive reads. Never cat a whole archive.

Recipes

Check current stream size

LOG=$LAZAR_HOME/logs/stream.jsonl
[ -f "$LOG" ] && wc -c "$LOG"

Pick the newest rotated archive

ARCHIVE=$(ls -t $LAZAR_HOME/logs/stream.jsonl.*.bak 2>/dev/null | head -n 1)
[ -n "$ARCHIVE" ] || { echo "no raw archive found"; exit 0; }

If an archive has already been pruned by the kernel, use the matching memory/log-summaries/<ts>.md summary as the durable record.

Read the full file on GitHub · 81 lines

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. 10d ago First seen · 81 lines · 0 tokens per session scan A 617751ac2ca9

Subscribe to this mod's changes

log-rotation is a skill published in the GitHub repository jasonkneen/lazar (31 stars, last pushed 29d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 964 tokens. 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens