Borrowing it
Nothing to install: this file belongs to ystreibel/logseq-wiki. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ystreibel/logseq-wiki/main/.skills/hermes-history-ingest/SKILL.mdgit clone --depth 1 https://github.com/ystreibel/logseq-wikiWrote 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/ystreibel/logseq-wiki/hermes-history-ingest)<a href="https://agentmods.dev/skills/ystreibel/logseq-wiki/hermes-history-ingest"><img src="https://agentmods.dev/badge/skills/ystreibel/logseq-wiki/hermes-history-ingest/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/ystreibel/logseq-wiki/hermes-history-ingest"><img src="https://agentmods.dev/badge/skills/ystreibel/logseq-wiki/hermes-history-ingest.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.00107 | $0.01681 |
| Opus 5 | $0.00053 | $0.00840 |
| Sonnet 5 | $0.00021 | $0.00336 |
| Haiku 4.5 | $0.00011 | $0.00168 |
Grade A, and why
hermes-history-ingest 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 11d 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hermes History Ingest — Conversation & Memory Mining for Logseq
REQUIRED: Invoke llm-wiki skill first for Logseq syntax and file format rules.
You are extracting knowledge from the user's Hermes agent history and distilling it into the Logseq wiki. Hermes stores both free-form memories and structured session transcripts — focus on durable knowledge, not operational telemetry.
This skill can be invoked directly or via the wiki-history-ingest router (/wiki-history-ingest hermes).
Before You Start
- Read
~/.logseq-wiki/configto getLOGSEQ_VAULT_PATHandHERMES_HISTORY_PATH(default to~/.hermesif unset) - Read
wiki/_manifest.jsonat the vault root to check what has already been ingested - Read
wiki/_master-index.mdat the vault root to understand what the wiki already contains
Ingest Modes
Append Mode (default)
Check wiki/_manifest.json for each source file. Only process:
- Files not in the manifest (new memory files, new session logs)
- Files whose modification time is newer than
ingested_atin the manifest
Use this mode for regular syncs.
Full Mode
Process everything regardless of manifest. Use after wiki-rebuild or if the user explicitly asks for a full re-ingest.
Hermes Data Layout
Hermes stores all local artifacts under ~/.hermes/ (or $HERMES_HOME for non-default profiles).
~/.hermes/
├── memories/ # Persistent agent memories (markdown or JSON)
│ └── *.md / *.json
├── skills/ # Installed skills (read-only for ingest purposes)
│ └── <skill-name>/SKILL.md
├── sessions/ # Session transcripts (if session logging is enabled)
│ └── YYYY-MM-DD/
│ └── <session-id>.jsonl
├── config.yaml # User config (model, theme, paths)
└── .hub/ # Skills Hub state (lock.json, audit.log, quarantine/)
Key data sources ranked by value
memories/*.md/memories/*.json— highest signal; curated persistent knowledge the agent accumulatedsessions/**/*.jsonl— structured turn-by-turn transcripts; rich but noisyconfig.yaml— metadata only; rarely worth ingesting
What ships with it
1 file 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.
- 11d ago First seen · 201 lines · 107 tokens per session scan A 437eacabdfc2
hermes-history-ingest is a skill published in the GitHub repository ystreibel/logseq-wiki (4 stars, last pushed 16d ago), licensed MIT. It adds 107 tokens to every session and 1,681 once invoked, about $0.0005 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
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.
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.…
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…
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.
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…
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.