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 reliquery-helpgit 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/reliquery-help)<a href="https://agentmods.dev/skills/the-essential/reliquery/reliquery-help"><img src="https://agentmods.dev/badge/skills/the-essential/reliquery/reliquery-help/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/the-essential/reliquery/reliquery-help"><img src="https://agentmods.dev/badge/skills/the-essential/reliquery/reliquery-help.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.00152 | $0.02894 |
| Opus 5 | $0.00076 | $0.01447 |
| Sonnet 5 | $0.00030 | $0.00579 |
| Haiku 4.5 | $0.00015 | $0.00289 |
Grade A, and why
reliquery-help 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 12d 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 — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Identity
Reliquery Help is the orientation guide for the entire system. It answers three questions: What do I have?, How does it work?, and How do I set it up? It performs no write operations — it reads, explains, and guides. Think of it as the help menu for the plugin.
Three modes — identify which the user needs:
- Overview mode: What Reliquery is and how the pieces fit together
- Tool reference mode: What MCP tools are available and what each does
- Setup mode: Installation, configuration, or troubleshooting
If unclear, start with a brief overview and ask what to dive into.
Overview — What Is Reliquery?
Reliquery is a context management and memory system for AI-assisted worldbuilding, co-writing, and roleplaying. It solves LLM statelessness: maintaining persistent, accurate lore across sessions without dumping an entire knowledge base into every prompt.
The name is a portmanteau of Relic + Query — querying the sacred artifacts of your creative vault.
Two Layers
The Vault — a folder of structured markdown files called relics, one per entity (character, location, faction, system, etc.), each with YAML frontmatter and [[wiki-link]] cross-references. The vault is the source of truth for all authored content. Reliquery creates and manages the vault folder structure itself — no special software required. The vault is just a folder of .md files.
Obsidian is optional but recommended. Obsidian is a free markdown editor that sits on top of the vault folder like a specialized file explorer with quality-of-life features: graph view to visualize entity connections, wiki-link navigation between relics, and plugin support (Dataview for queryable tables, Templater for relic scaffolding). Think of it as a secondary UI layer — it adds organization, editing, and visualization tools, but the vault works without it. You can use VS Code, Notepad, Google Drive, or any tool that edits markdown files.
The Palace (MemPalace) — a local-first AI memory system built on ChromaDB (vector search) and SQLite (knowledge graph). It stores verbatim chunks of vault content as searchable drawers, organized into a spatial hierarchy: Wings → Rooms → Drawers. The palace is how Claude remembers your vault between sessions.
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.
- 12d ago First seen · 247 lines · 152 tokens per session scan A bfa118ac5f20
reliquery-help is a skill published in the GitHub repository the-essential/reliquery (5 stars, last pushed 3mo ago), licensed MIT. It adds 152 tokens to every session and 2,894 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.