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 Jessinra/Lorekeeper --skill lorekeeper-marketinggit clone --depth 1 https://github.com/Jessinra/LorekeeperWrote 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/jessinra/lorekeeper/lorekeeper-marketing)<a href="https://agentmods.dev/skills/jessinra/lorekeeper/lorekeeper-marketing"><img src="https://agentmods.dev/badge/skills/jessinra/lorekeeper/lorekeeper-marketing/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/jessinra/lorekeeper/lorekeeper-marketing"><img src="https://agentmods.dev/badge/skills/jessinra/lorekeeper/lorekeeper-marketing.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.00056 | $0.01592 |
| Opus 5 | $0.00028 | $0.00796 |
| Sonnet 5 | $0.00011 | $0.00318 |
| Haiku 4.5 | $0.00006 | $0.00159 |
Grade A, and why
lorekeeper-marketing 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 9d 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lorekeeper Marketing
User-facing content workflow for the Lorekeeper project.
Core Principles
All Lorekeeper marketing copy must follow these non-negotiables:
- Don't burn bridges — tech ecosystems thrive when there's a lot of contribution from open source and adoption. Never undermine competing tools. Acknowledge them by name where relevant; name-dropping peers is generous, not threatening.
- Cooperative tone always — even in comparison tables. Frame differences as trade-offs, not deficiencies. "Optimised for X" beats "worse at Y".
- Own our strengths, don't exaggerate — local-first, self-improving quality loop, zero ops, built by agents using agents, free to run forever. These are real. Lead with them.
- Honest about trade-offs — the 1.4GB model weight is real. Benchmarks pending. Cloud not yet available. Say so upfront. Trust compounds when you don't oversell.
- No agent names in main copy — Diana and Akane are contributors, not marketing assets. Credits section only (end of doc), never in hero or manifesto body.
Key Positioning
Tagline: Self-improving memory for AI agents. One command, no cloud, no config.
The mechanism that makes us different:
Agent uses a memory → rates it useful or not →
scores adjust automatically → weak memories fade →
strong memories surface more often → search gets sharper
A six-month-old install is genuinely different from a fresh install. Nobody else has this.
Our niche: Solo developers and agent workflows where zero ops, zero cloud, and a self-improving store matter most. Cloud services and Docker-based solutions serve teams and production apps well — we're the other end of that spectrum.
Manifesto location: docs/manifesto.md — the short public-facing statement of values.
Positioning deep-dive: docs/positioning-manifesto.md — internal strategy reference.
README Structure (canonical order)
- Hero block — tagline + install command + one-liner hook
- Why Lorekeeper — problem story, cooperative landscape framing, our niche
- Quick Start — install → setup → connect → first memory
- Use Cases — 4 scenarios (session continuity, multi-agent, debugging, onboarding)
- Who It's For — explicit in/out
- How It Compares — table with cooperative framing sentence above and below
- Features table
- MCP Tools — full API reference
- Performance — benchmarks (LKPR-70) or honest stub
- Dashboard — screenshots
- Built by Agents — dogfooding story
- Setup (git clone) — dev path
- Development — test/lint commands
- Project Layout
- License
- Footer — links to manifesto + strategy docs
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.
- 9d ago First seen · 168 lines · 56 tokens per session scan A b7250d876f0b
lorekeeper-marketing is a skill published in the GitHub repository Jessinra/Lorekeeper (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 56 tokens to every session and 1,592 once invoked, about $0.0003 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
copywriter
Write compelling copy for web, marketing, and product surfaces. Use when the user needs UX writing, landing page copy, CTAs, product messaging, or other persuasive user-facing text.
create-modal
Create declarative modals using the modal library API. Covers modal types (confirm, input, select, form), sections (Text, Buttons, Input, Textarea, Checkbox, Select, List, Combo, When, Custom), rendering with OverlayModal, and keyboard/mouse handling. Use when adding modals or dialogs to the application.
create-plugin
Create new sidecar plugins implementing the plugin.Plugin interface, rendering views with Bubble Tea, handling keyboard input via keymap contexts, and integrating with the app shell (footer hints, event bus, adapters). Use when creating a new plugin, modifying plugin architecture, or debugging plugin…
merge-strategy
Git merge strategies, conflict resolution approaches, merge vs rebase recommendations, and branch integration patterns in sidecar. Covers pull strategy menu, direct merge workflow, squash merge, commit message templates, configurable defaults, and protected branches. Use when working on git merge features or making…
keyboard-shortcuts
Reference for keyboard shortcut implementation, keybinding registration, shortcut parity with vim and other TUI tools, and the complete shortcut assignment table across all sidecar plugins. Use when adding or modifying keyboard shortcuts, checking shortcut assignments, resolving key conflicts, or assessing alignment…
memory-audit-pattern-extraction
A method for investigating repeated mistakes by comparing related memories and checking whether an earlier reminder failed. It looks at where the reminder was stored, when it was created, and whether it was strong enough to prevent the mistake.