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 koersliven/Lore --skill lore-evolvegit clone --depth 1 https://github.com/koersliven/LoreWrote 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/koersliven/lore/lore-evolve)<a href="https://agentmods.dev/skills/koersliven/lore/lore-evolve"><img src="https://agentmods.dev/badge/skills/koersliven/lore/lore-evolve/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/koersliven/lore/lore-evolve"><img src="https://agentmods.dev/badge/skills/koersliven/lore/lore-evolve.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.00014 | $0.01597 |
| Opus 5.5 | $0.00006 | $0.00639 |
| Sonnet 5.5 | $0.00003 | $0.00319 |
| Haiku 4.5 | $0.00001 | $0.00160 |
Grade A, and why
lore-evolve 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 1mo 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/evolve — Snapshot Compilation
When to Trigger
- User explicitly invokes this skill
- Stop hook detects 10+ rounds of accumulated knowledge (hard limit)
- Periodic maintenance (agent notices many uncompiled increments)
- After a major feature completion or PR merge
Purpose
Compile all accumulated increment files into a single, coherent .ai-context/snapshot.md — the agent's "long-term memory" of the project. This is the project's living architecture document that grows more accurate with each compilation.
Process
Step 0: Detect Modular Mode
Check if .ai-context/modules/ directory exists.
- If no → Check if this is the first compile with sufficient module-scoped knowledge. If snapshot.md has knowledge entries with file references that can be mapped to code directories, auto-trigger modular partitioning by executing /lore-modularize before proceeding. Then run legacy evolve if no modules were discovered.
- If yes → Run modular evolve path (Steps 1-8 below).
Step 1: Read Current State
Read:
.ai-context/snapshot.md— current snapshot (may not exist for first compile).ai-context/modules/_index.md— module registry (if modular mode)- For each known module, read
modules/<name>/knowledge.md - All files in
.ai-context/increments/— sorted by date (oldest first) - For each module, read
modules/<name>/increments/ .ai-context/config.yaml— project configuration
Step 2: Route Increments by Domain
For each uncompiled increment (global or per-module):
Determine target:
- Has
domain: <module-name>meta field AND module exists in_index.md→ target that module'sknowledge.md - No
domainfield butaffected_filespaths match a module's code path → infer domain, target that module - No
domainand no file path match → target globalsnapshot.md domainreferences unknown module → create warning, route to globalsnapshot.md
Step 3: Conflict Detection (per-target)
For each new increment, check against its target (snapshot.md or modules//knowledge.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.
- 1mo ago First seen · 190 lines · 14 tokens per session scan A ed83c325b17b
lore-evolve is a skill published in the GitHub repository koersliven/Lore (5 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 14 tokens to every session and 1,597 once invoked, about $0.0001 per session on Opus 5.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
context-end
Close a workspace session by reviewing a proposed summary, recording approved outcomes, updating state and decisions, and checking repository safety. Use only when the user explicitly asks to end, close, or hand off the current session.
context-update
Save a brief mid-session checkpoint to this workspace and update current state only when a priority or open thread changed. Use only when the user explicitly asks to checkpoint or save current progress.
faf-expert
Expert in .faf (Foundational AI-context Format) files for persistent project context. Use when working with .faf files, project DNA, CLAUDE.md bi-sync, faf-cli commands, MCP server configuration, or AI-readiness scoring (0-100%). Updated for v2.8.0 Tool Visibility System.
contextos-workspace
Run Context OS continuity and lifecycle workflows in a user-selected Context OS workspace. Use when asked to inspect, set up, update, or close a Context OS session.
personal-context
Interview the user to build or update a reusable "about me" context file for AI tools — who they are, their role and background, how they work, and how they want AI to help. Use when the user says "build my personal context", "create my about-me context", "set up my AI context", "update my personal context", or wants…
refresh-context
Review and refresh an existing personal-context.md or company-context.md — check what has gone stale, fill gaps against the current template, and update the file. Use when the user says "refresh my context", "review my context", "is my context still up to date", "my context is stale", or after a change in role, offer…