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 jasonkneen/lazar --skill log-harvestgit clone --depth 1 https://github.com/jasonkneen/lazarWrote 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/jasonkneen/lazar/log-harvest)<a href="https://agentmods.dev/skills/jasonkneen/lazar/log-harvest"><img src="https://agentmods.dev/badge/skills/jasonkneen/lazar/log-harvest/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.
<a href="https://agentmods.dev/skills/jasonkneen/lazar/log-harvest"><img src="https://agentmods.dev/badge/skills/jasonkneen/lazar/log-harvest.svg" alt="Reviewed on agentmods" width="80" 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.00099 | $0.00692 |
| Opus 5 | $0.00049 | $0.00346 |
| Sonnet 5 | $0.00020 | $0.00138 |
| Haiku 4.5 | $0.00010 | $0.00069 |
Grade A, and why
log-harvest 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.
log-harvest — make my own history durable and searchable
Raw logs/stream.jsonl (+ rotated .bak/.bak.gz archives) is where my real history lives, but it's multi-MB JSONL I can't hold in context. If I lose it, I lose the memory of my own work (on 2026-07-08 I told the operator a real page they built "didn't exist"). This skill harvests the logs into a durable record so that stops happening.
Two layers — both matter
- Mechanical harvest (this skill,
harvest.sh) — cheap, no LLM, repeatable. Extracts per archive: date range, the real user prompts (topics), and files I created/edited →memory/work-journal.md. This is my navigation index:rg <topic> memory/work-journal.mdto find when/what. - LLM distillation (
_meta/distill) — judgment, costs a call per archive. Extracts gotchas/recipes/conventions/preferences →memory/distilled/. This is my learnings layer.
The logs are only safely disposable once BOTH have run over them.
Run it
bash skills/_meta/log-harvest/harvest.sh
Idempotent — a marker (memory/.harvested) records processed archives; re-runs only add new material. The live stream.jsonl is always re-scanned (it grows).
HONEST LIMITS (evaluated 2026-07-08 — do not oversell this)
- Mechanical harvest is LOSSY. It caps prompts/files per section and its file-path regex misses some writes (it missed a real
pricing-component/index.html). It is a navigation index, NOT a lossless archive. - Therefore: do NOT fully delete raw logs after harvesting. The right disposability protocol is:
- Compress, don't delete.
gzipany uncompressedstream.jsonl.*.bak(rotated archives are already superseded in the live log). Gzipped archives are cheap cold storage and the ground-truth fallback. - Keep
memory/work-journal.md+memory/distilled/as the hot layer I actually read. - Only delete a raw archive if disk genuinely forces it AND it's both harvested and distilled — and even then prefer keeping the gzip.
- Compress, don't delete.
- NEVER pattern-delete under
memory/distilled/. Distilled files are named<archive>.bak.md, so a naive*.bak.*cleanup eats real learnings (I did this to two files on 2026-07-08). Whitelistmemory/distilled/in any cleanup.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 35 lines · 99 tokens per session scan A 94aa9c2bb28a
log-harvest is a skill published in the GitHub repository jasonkneen/lazar (31 stars, last pushed 29d ago), licensed MIT. It adds 99 tokens to every session and 692 once invoked, about $0.0005 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-30.
Other skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.