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 the-essential/reliquery --skill chroniclegit clone --depth 1 https://github.com/the-essential/reliqueryWrote 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/the-essential/reliquery/chronicle)<a href="https://agentmods.dev/skills/the-essential/reliquery/chronicle"><img src="https://agentmods.dev/badge/skills/the-essential/reliquery/chronicle.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.1 | $0.00166 | $0.03740 |
| Opus 5 | $0.00083 | $0.01870 |
| Sonnet 5 | $0.00033 | $0.00748 |
| Haiku 4.5 | $0.00017 | $0.00374 |
Grade A, and why
chronicle 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 7d 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 — 304 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Identity
Chronicle is the steward of the vault — the pipeline that turns raw content into relics: structured files that preserve a world's (or project's) accumulated knowledge.
Relics are not disposable documentation. They are the accumulated creative record of a living body of work, shaped by the author over time and entrusted to the vault for safekeeping. Chronicle treats them accordingly: read carefully before touching, altered only with explicit permission, never overwritten without a backup in place. The author's choices are sovereign. Chronicle's purpose is to preserve, extend, and illuminate them — not to second-guess or silently "improve" them. When uncertain, do less and ask more.
There are three input modes — identify which applies before proceeding:
- Extract mode: User shares content (manuscript, session log, scene draft, research) to mine for knowledge
- Reconstruct mode: A relic was deleted or lost; rebuild it from memory sources
- Audit mode: User wants to check what's covered, what's missing, or what needs updating
Session File Log
Chronicle maintains a running log of every relic file it creates, updates, or skips during the session. This log lives in conversation context only (not persisted to disk) and serves three purposes:
- Progress tracking — the user can ask "what have we filed so far?" at any point
- Handoff to memorize — after committing, the log tells memorize exactly which files need indexing
- Rollback scope — if something goes wrong, it identifies exactly which vault files were touched
Per file, track: filename, vault path, action (created / updated / skipped), and a one-line summary of what changed.
Start the log at Phase 3; reference it in Phase 7 and the handoff to memorize.
Phase 1 — Memory & Context Scan
Before generating anything, gather everything already known. Writing without reading first is how worlds get contradicted.
1a — Load the palace
Call mempalace_status to verify the memory system is live and load the palace layout.
What ships with it
2 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.
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.
- 7d ago First seen · 304 lines · 166 tokens per session scan A 0a7c9a3d1b2b
chronicle is a skill published in the GitHub repository the-essential/reliquery (5 stars, last pushed 3mo ago), licensed MIT. It adds 166 tokens to every session and 3,740 once invoked, about $0.0008 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
weekly-digests
Generate a serial week-by-week narrative digest of a project's full claude-mem timeline. Splits the timeline into per-ISO-week files, then runs one consecutive subagent per week — each receiving the prior week's carry-forward block — to produce one chapter per ISO week of data. Use when asked for "weekly digests"…
cloud-sync
Set up or check claude-mem cloud sync with cmem.ai Pro. Use when the user says "set up cloud sync", "sync my memories", "cmem pro", "cloud backup", "sync status", or wants their memory database backed up or synced to their cmem.ai account.
hivemind-memory
Global team and org memory powered by Activeloop. ALWAYS check BOTH built-in memory AND Hivemind memory when recalling information.
init
Install or update OwnMem in the current repository. Use when the user asks to set up OwnMem, add local project memory for coding agents, or refresh an existing OwnMem installation after a version bump.
mnemo-cortex
Installs and wires Mnemo Cortex (local-first persistent memory) into OpenClaw and other MCP-capable agents. Use for cross-session recall, decision history, or multi-agent shared memory.
honcho-integration
Integrate Honcho memory into existing Python or TypeScript codebases. Use when adding Honcho SDK, setting up peers, configuring sessions, and accessing Honcho's representation.