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/theadust/lore/skillnpx skills add TheaDust/lore --skill skillgit clone --depth 1 https://github.com/TheaDust/loreWhat 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.00141 | $0.04935 |
| Opus 5 | $0.00071 | $0.02468 |
| Sonnet 5 | $0.00028 | $0.00987 |
| Haiku 4.5 | $0.00014 | $0.00494 |
Grade A, and why
lore 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 2d 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 — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
lore — Framework-agnostic Memory Management
What this skill is
A long-term knowledge base for a software project, maintained by AI agents. It is not a dev journal or a changelog. It captures the kind of context that normally lives only in the original developer's head:
- What the project is, how it is shaped (architecture)
- Why specific choices were made over alternatives (decisions)
- How code should be written and what to avoid (conventions)
This knowledge is persisted as plain Markdown files in .lore/ at the project root. Any agent that can read files can consume them.
When to trigger
The skill uses a two-tier trigger model.
Tier 1 — Loading the skill
Load this skill when the user explicitly invokes lore, names a subcommand, references .lore/, or asks to record, recall, audit, sync, or compress project memory about decisions, architecture, conventions, or monorepo scopes. Generic phrases like "init", "compress", "audit", or "query" alone are not enough — they may map to the agent's native commands or unrelated tasks (Claude Code's /init, /compact, security audits, SQL queries, etc.).
| User says (examples) | Command |
|---|---|
| "lore init" / "create lore memory bank" / "initialize lore" | init |
| "lore sync" / "sync this change to lore" / "record this decision in lore" | sync |
| "lore query" / "query lore" / "what's the project convention" | query |
| "lore audit" / "check lore" / "is memory still accurate" | audit |
| "lore compress" / "compress lore" / "summarize lore" | compress |
| "lore mirror" / "update CLAUDE.md" / "refresh mirror" | mirror |
| "lore history" / "show the git history of this entry" / "show me the commits behind this" | history |
Tier 2 — Internal proposals (after the skill is loaded)
Once the skill is loaded for this session, certain commands may proactively propose themselves based on internal thresholds. Writes follow the configured trust controls: confirmation-required changes wait for the user, while permitted auto-applied changes are reported after writing.
What ships with it
17 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/audit-template.md 2.9 KB
- references/compatibility.md 11 KB
- references/config.md 6.4 KB
- references/entry-format.md 6.4 KB
- references/history-command.md 7.1 KB
- references/monorepo-detection.md 2.3 KB
- references/platform-mirrors.md 18 KB
- references/stale-new-markers.md 4.3 KB
- references/summary-template.md 3.2 KB
- references/workflows.md 22 KB
- scripts/find_duplicates.py 6.7 KB runs code
- scripts/find_stale.py 5.2 KB runs code
- scripts/history.py 25 KB runs code
- scripts/id_hash.py 1.1 KB runs code
- scripts/list_entries.py 8.7 KB runs code
- scripts/README.md 6.7 KB
- scripts/README.zh-CN.md 6.3 KB
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.
- 2d ago First seen · 240 lines · 141 tokens per session scan A 79a666fb9b27
lore is a skill published in the GitHub repository TheaDust/lore (23 stars, last pushed 3d ago), licensed MIT. It adds 141 tokens to every session and 4,935 once invoked, about $0.0007 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
gpt-researcher
GPT Researcher is an autonomous deep research agent that conducts web and local research, producing detailed reports with citations. Use this skill when helping developers understand, extend, debug, or integrate with GPT Researcher - including adding features, understanding the architecture, working with the API…
ai-style
当任务是用中文撰写或改写面向读者的文案（产品发布稿、公众号文章、邮件、README 等）， 或用户反馈文字「AI 味太重」「不像人写的」时，加载本 Skill。.
triage
你是当前任务的分诊协调者。先识别用户的全部目标、顺序依赖和验收条件，再按 “事实检索 → 计算/执行 → 写作”顺序逐步请求切换到需要的专业能力。不要替专业 能力完成它的工作，也不要在信息缺失时臆造结果。.
writing
将共享历史中的已验证事实和计算结果整理成符合受众、格式与长度约束的成稿。.
gpt-researcher
Autonomous deep research from Codex via MCP.
data_analysis
基于已确认数据执行可审计的数学计算和描述统计。.