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 liza-mas/liza --skill lesson-capturegit clone --depth 1 https://github.com/liza-mas/lizaWrote 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/liza-mas/liza/lesson-capture)<a href="https://agentmods.dev/skills/liza-mas/liza/lesson-capture"><img src="https://agentmods.dev/badge/skills/liza-mas/liza/lesson-capture/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/liza-mas/liza/lesson-capture"><img src="https://agentmods.dev/badge/skills/liza-mas/liza/lesson-capture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.01503 |
| Opus 5 | $0.00010 | $0.00751 |
| Sonnet 5 | $0.00004 | $0.00301 |
| Haiku 4.5 | $0.00002 | $0.00150 |
Grade A, and why
lesson-capture 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Objective
Extract a lesson from the current conversation context and persist it as a structured file. Lessons are project-specific operational knowledge — gotchas, patterns, and hard-won insights that prevent recurring mistakes.
Lessons complement the contract: the contract governs how to work (behavioral, project-agnostic); lessons capture what we learned here (operational, project-specific).
Audience
Lessons are split by audience:
| Audience | Directory | Discovery | Content |
|---|---|---|---|
| Agents | lessons/agents/ |
GUARDRAILS.md trigger index |
Project-specific gotchas agents hit repeatedly |
| Humans | lessons/humans/ |
lessons/humans/README.md |
Workflow habits, domain pitfalls, invariants to preserve |
If audience is ambiguous, ask.
Lesson Format
Each lesson is a small .md file with yaml frontmatter.
---
title: "Descriptive title"
trigger: "When [succinct situational condition]"
keywords: [keyword1, keyword2, keyword3]
date: YYYY-MM-DD
---
## Context
[Situation, intent, and conditions that led to this lesson]
## Failure Mode
[What went wrong and why]
## Solution
[What to do instead]
## References
- [Links to relevant files, docs, specs, or external resources]
Frontmatter fields:
- title: What the lesson is about (noun phrase)
- trigger: When to consult this lesson (action phrase, starts with "When")
- keywords: Concrete terms for matching — error messages, class names, tool names, file patterns
- date: When the lesson was captured
Body sections:
- Context: Enough detail to recognize the situation. Not a narrative — a pattern description.
- Failure Mode: The specific thing that goes wrong. Name the mechanism, not just the symptom.
- Solution: Concrete, actionable. Code snippets or commands when applicable.
- References: Links to files, docs, specs, external resources. Keep it short.
Index Format
| Audience | Location |
|---|---|
| Agents | GUARDRAILS.md (Tier 2) |
| Humans | lessons/humans/README.md |
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 · 163 lines · 19 tokens per session scan A 996fed171358
lesson-capture is a skill published in the GitHub repository liza-mas/liza (382 stars, last pushed 2d ago), licensed Apache-2.0. It adds 19 tokens to every session and 1,503 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-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…
shellm
Reference for the shellm system — recursive LLM shell, identity management, memory, skills, trajectory, and all CLI tools. Use when working on shellm itself, debugging agent behavior, or understanding how the pieces fit together.