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/ystreibel/logseq-wiki/wiki-agentnpx skills add ystreibel/logseq-wiki --skill wiki-agentgit 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/wiki-agent)<a href="https://agentmods.dev/skills/ystreibel/logseq-wiki/wiki-agent"><img src="https://agentmods.dev/badge/skills/ystreibel/logseq-wiki/wiki-agent.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.00190 | $0.03659 |
| Opus 5 | $0.00095 | $0.01829 |
| Sonnet 5 | $0.00038 | $0.00732 |
| Haiku 4.5 | $0.00019 | $0.00366 |
Grade A, and why
wiki-agent 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 5d 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 — 295 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wiki Agent — Targeted Cross-Agent History Search + Ingest
You are doing a query-driven targeted ingest from one specific AI agent's raw conversation history. The user is typically working in a different agent right now and wants to pull in context from another agent's past sessions.
This is not bulk ingest. You find sessions about a specific topic, extract the relevant blobs, distill them into the wiki, and return a synthesized answer the user can act on immediately.
Command Routing
Parse the invocation to determine the target agent and optional query:
| Command | Target | Example |
|---|---|---|
/wiki-claude [query] |
Claude Code history | /wiki-claude "how did I set up auth middleware" |
/wiki-codex [query] |
Codex CLI history | /wiki-codex "rust ownership patterns" |
/wiki-hermes [query] |
Hermes agent history | /wiki-hermes "memory architecture" |
/wiki-openclaw [query] |
OpenClaw history | /wiki-openclaw "project planning approach" |
/wiki-copilot [query] |
Copilot chat history | /wiki-copilot "test strategy for API routes" |
/wiki-pi [query] |
Pi agent history | /wiki-pi "how did I refactor the auth module" |
If no query is given, default to recent sessions mode: ingest the last 5 unprocessed sessions from that agent and return a summary of what was found. This is equivalent to a focused wiki-history-ingest for that agent only.
Before You Start
- Resolve config — read
~/.logseq-wiki/configfirst (givesLOGSEQ_VAULT_PATHandLOGSEQ_WIKI_REPO). If absent, fall back to.envin the logseq-wiki repo. If neither exists, prompt the user to runbash setup.sh. - Read
$LOGSEQ_VAULT_PATH/wiki/_manifest.json→ know what's already ingested. - Read
$LOGSEQ_VAULT_PATH/wiki/_hot.mdif it exists → warm context on recent wiki activity.
Step 1: Locate the Agent's History Root
| Agent | Default path | Config override |
|---|---|---|
claude |
~/.claude + ~/Library/Application Support/Claude/local-agent-mode-sessions/ |
CLAUDE_HISTORY_PATH in .env |
codex |
~/.codex |
CODEX_HISTORY_PATH in .env |
hermes |
~/.hermes |
HERMES_HOME in env or .env |
openclaw |
~/.openclaw |
OPENCLAW_HOME in .env |
copilot |
~/.copilot |
COPILOT_HISTORY_PATH in .env |
pi |
~/.pi/agent/sessions |
PI_HISTORY_PATH in .env |
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.
- 5d ago First seen · 295 lines · 190 tokens per session scan A 286f8ae21b25
wiki-agent is a skill published in the GitHub repository ystreibel/logseq-wiki (4 stars, last pushed 10d ago), licensed MIT. It adds 190 tokens to every session and 3,659 once invoked, about $0.0010 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…
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
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…