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 agentmods add skills/labyrinth-analytics/loreconvo/lore-onboardnpx skills add labyrinth-analytics/loreconvo --skill lore-onboardgit clone --depth 1 https://github.com/labyrinth-analytics/loreconvoWrote 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/labyrinth-analytics/loreconvo/lore-onboard)<a href="https://agentmods.dev/skills/labyrinth-analytics/loreconvo/lore-onboard"><img src="https://agentmods.dev/badge/skills/labyrinth-analytics/loreconvo/lore-onboard.svg" alt="Measured on agentmods" 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 | $0.00081 | $0.01263 |
| Opus 5 | $0.00041 | $0.00632 |
| Sonnet 5 | $0.00016 | $0.00253 |
| Haiku 4.5 | $0.00008 | $0.00126 |
Grade A, and why
lore-onboard 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 4d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 4d ago First seen · 145 lines · 81 tokens per session scan A 22d316bd7539
lore-onboard is a skill published in the GitHub repository labyrinth-analytics/loreconvo (10 stars, last pushed yesterday), with no licence file. It adds 81 tokens to every session and 1,263 once invoked, about $0.0004 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-31.
Other skills, from other repositories
redis
Redis in-memory data store patterns for caching, sessions, queues, and real-time features.
crestapps-core-postgresql
Skill for integrating PostgreSQL pgvector indexing data sources documents vector retrieval and memory in CrestApps.Core.
notion
Read, create, and update Notion pages and databases via the Notion REST API.
hmem-write
Hmem write protocol — picks prefix (L/E/D/P/N/R/I/H…), tree location, and tags, and detects duplicates before persisting. Use before any writememory or appendmemory call (skipping it creates duplicates and misplaced entries), or when the user says 'remember this', 'save this', 'log this', or invokes /hmem-write.
hmem-config
View and change hmem memory settings, hooks, sync, and checkpoints. Use on /hmem-config, or when the user asks why context is huge, how to change auto-save, how often checkpoints fire, or how to set up sync.
hmem-read
Load long-term memory from hmem via readmemory or loadproject. Use when starting fresh with no L1 summaries, after /compact, when the user asks 'what do you remember', 'continue where we left off', 'was war der letzte Stand', or about a project/topic visible in L1 summaries. Covers search, prefix filter, findrelated…