lore-brief

lore-brief is a skill for Claude Code, Codex from jordanhindo/lore. It costs 69 tokens per session (580 once invoked), scanned A, original, MIT.

A read-only daily continuity brief generated from Lore, a system for storing and recalling project information. It summarises recent work with cited evidence and suggests possible follow-up objects without creating them.

In plain words
What is it for?
Use it for daily recaps, continuity summaries, scheduled read-only reviews, and proposing next actions from Lore. It does not create jobs, issues, tasks, memory cards, code, or automations unless separately requested.
Why use it?
It reduces the need to reconstruct what happened recently and keeps completed work, open tasks, learned signals, and possible contradictions together with their evidence.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it for daily recaps, continuity summaries, scheduled read-only reviews, and proposing next actions from Lore. It does not create jobs, issues, tasks, memory cards, code, or automations unless separately requested.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jordanhindo/lore/lore-brief
Install

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.

Any agent
npx skills add jordanhindo/lore --skill lore-brief
Clone the repo
git clone --depth 1 https://github.com/jordanhindo/lore

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for lore-brief

README.md
[![agentmods](https://agentmods.dev/badge/skills/jordanhindo/lore/lore-brief/github.svg)](https://agentmods.dev/skills/jordanhindo/lore/lore-brief)
Your own site
<a href="https://agentmods.dev/skills/jordanhindo/lore/lore-brief"><img src="https://agentmods.dev/badge/skills/jordanhindo/lore/lore-brief/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.

agentmods 80×15 button for lore-brief

Your own site · 80×15
<a href="https://agentmods.dev/skills/jordanhindo/lore/lore-brief"><img src="https://agentmods.dev/badge/skills/jordanhindo/lore/lore-brief.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 69 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 580 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00069 $0.00580
Opus 5 $0.00034 $0.00290
Sonnet 5 $0.00014 $0.00116
Haiku 4.5 $0.00007 $0.00058

Measured 9d ago against content hash ced66e7f3abc, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

lore-brief 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.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/validate-brief.mjs), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/lore-brief/SKILL.md · 42 lines

How it starts

The opening of the file, as written. The whole thing — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Lore Brief

Use this when the user wants a continuity brief, daily recap, or proposal-only synthesis from Lore. Default window is the rolling last 24 hours ending at run time unless the user supplies a window.

Workflow

  1. Compute retrieval bounds: local date label for humans, explicit ISO fromIso/toIso values for output and --since/--until values for Lore commands.
  2. Run lore status --json --since <iso> --until <iso> and stop on unhealthy status. If status is possibly_unsynced and schemaVersion is greater than supportedSchemaVersion, do not recommend bare lore sync as sufficient; say Lore must be updated before write/sync recovery can refresh the window.
  3. Use lore-recall evidence packet rules for searches and citations.
  4. Produce a brief with sideEffects: false.
  5. Propose follow-up objects only. Do not create jobs, issues, wiki pages, skills, tasks, memory cards, code, or automations unless the user asks as a follow-up.

Output Sections

  • window: fromIso, toIso, timeZone, localDateLabel.
  • completedActivity: evidence-backed work that finished in the window.
  • openWork: unresolved work with cited ids or marked uncited.
  • changes: evidence-backed changes to code, docs, skills, workflow, setup, or state.
  • learnedSignals: things discovered while briefing.
  • proposals: read-only suggestions using references/proposal-vocabulary.md.
  • memoryCardCandidates: decision, claim, commitment, artifact, contradiction, open_question.
  • contradictionCandidates: both sides with evidence, no averaging.
  • gaps: optional notes for what Lore could not prove.

Rules

  • Always state sideEffects: false.
  • Scheduled use is read-only synthesis, never mutation authority.
  • Date labels shown to the user use local timezone; retrieval filters use explicit ISO instants.
  • Contradictions preserve both sides and evidence. Do not resolve unless current artifacts prove a side.
  • If evidence is stale, label it and propose verification instead of acting.

Read the full file on GitHub · 42 lines

Files

What ships with it

7 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.

Changes

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.

  1. 9d ago First seen · 42 lines · 69 tokens per session scan A ced66e7f3abc

Subscribe to this mod's changes

lore-brief is a skill published in the GitHub repository jordanhindo/lore (14 stars, last pushed 2mo ago), licensed MIT. It adds 69 tokens to every session and 580 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-30.

Related

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.

garrytan/gbrain · 52 tokens

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.…

mem0ai/mem0 · 273 tokens

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…

danielmiessler/LifeOS · 196 tokens

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.

opensquilla/opensquilla · 44 tokens

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…

shiwenwen/hope-agent · 115 tokens

establishing-project-context

Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.

GanyuanRan/Aegis · 45 tokens