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 archive-searchgit 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/archive-search)<a href="https://agentmods.dev/skills/jasonkneen/lazar/archive-search"><img src="https://agentmods.dev/badge/skills/jasonkneen/lazar/archive-search/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/archive-search"><img src="https://agentmods.dev/badge/skills/jasonkneen/lazar/archive-search.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.00000 | $0.01101 |
| Opus 5 | $0.00000 | $0.00550 |
| Sonnet 5 | $0.00000 | $0.00220 |
| Haiku 4.5 | $0.00000 | $0.00110 |
Grade A, and why
archive-search 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
archive-search
Search across rotated log archives ($LAZAR_HOME/logs/stream.jsonl.*.bak) when you can't find what you need in current stream.jsonl or in memory/log-summaries/.
This is the L3 tier of lazar's three-tier memory. Use it when L1 (current log) and L2 (summaries in memory) don't have the answer. It is never the first move — by the time you reach for archives you should already know roughly which time window to look in, because L2 summaries tell you the date range covered by each .bak file.
When to use
- The user references a session, command, or decision older than what's in current
stream.jsonl. - L2 summaries (
cat $LAZAR_HOME/memory/log-summaries/*.md) point at a specific archive. - You're doing forensic recall of a specific tool call, exact prompt, or full transcript from a past invocation.
Hard rules
- NEVER
cat $LAZAR_HOME/logs/stream.jsonl.*.bak. Archives can be 10MB each — globbing them all into one cat will absolutely blow context. - Always use
rgwith bounds. Process one archive at a time, pipe throughtail -corhead -n. - Read L2 first. Each
.bakarchive has a sibling summary atmemory/log-summaries/<ts>.md. Read those to figure out which archive to search before touching one.
Recipes
Decide which archive to search (do this first)
ls -la $LAZAR_HOME/memory/log-summaries/
cat $LAZAR_HOME/memory/log-summaries/*.md | head -n 100 # bounded scan of all summaries
List archives by age
ls -lat $LAZAR_HOME/logs/stream.jsonl.*.bak
The filename embeds a unix timestamp: stream.jsonl.<ts>.bak. Bigger number = newer.
Search ONE archive for a topic
rg -i "topic-keyword" $LAZAR_HOME/logs/stream.jsonl.<TS>.bak | tail -n 50
Find a specific user prompt across all archives (bounded)
for f in $LAZAR_HOME/logs/stream.jsonl.*.bak; do
jq -r 'select(.kind == "user") | "\(.ts_ms) \(.content)"' "$f" 2>/dev/null \
| rg -i "your-search" \
| tail -n 5
done | tail -n 30
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 · 85 lines · 0 tokens per session scan A a2b5ae30e2d7
archive-search is a skill published in the GitHub repository jasonkneen/lazar (31 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,101 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.
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.