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 instructions/ystreibel/logseq-wiki/agents-mdgit clone --depth 1 https://github.com/ystreibel/logseq-wikiWhat 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 | $0.02042 | $0.02042 |
| Opus 5 | $0.01021 | $0.01021 |
| Sonnet 5 | $0.00408 | $0.00408 |
| Haiku 4.5 | $0.00204 | $0.00204 |
Grade A, and why
logseq-wiki AGENTS.md 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 3d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- logseq-wiki CLAUDE.md — 95% identical, 14 lines differ
How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
logseq-wiki — Agent Context
A skill-based framework for building and maintaining a Logseq knowledge base using the LLM Wiki pattern (inspired by Andrej Karpathy's gist). No scripts, no API keys — markdown instructions that you execute directly.
Configuration
Read config in this order (first found wins):
~/.logseq-wiki/config— global config, works from any project directory.envin the logseq-wiki repo — local fallback
Both files set LOGSEQ_VAULT_PATH (where the Logseq vault lives). The global config also sets LOGSEQ_WIKI_REPO (where this repo is cloned).
Vault Structure
Logseq vaults have a specific structure — skills must respect it:
$LOGSEQ_VAULT_PATH/
├── pages/ # User's pages (READ ONLY — never modify)
├── journals/ # Daily notes YYYY_MM_DD.md (READ ONLY)
├── assets/ # Images, PDFs referenced in notes (READ ONLY)
├── logseq/ # Logseq config (READ ONLY)
└── wiki/ # Generated wiki (READ + WRITE)
├── _master-index.md
├── _manifest.json
├── _log.md
├── _meta/
│ └── taxonomy.md
├── _archive/ # Wiki snapshots (rebuild/restore)
└── [thème]/
├── _index.md
└── [page].md
Every wiki page uses Logseq property syntax (title:: value, never YAML frontmatter). Pages connect via [[wiki/thème/page]] namespace links.
Skill Routing
Skills live in .skills/<name>/SKILL.md. Match the user's intent to the right skill:
| User says something like… | Skill |
|---|---|
| "initialise mon wiki" / "setup" / "set up my wiki" | wiki-setup |
| "ingère mon vault" / "ingest complet" / "distille mes notes" | wiki-ingest |
| "mets à jour mon wiki" / "update wiki" / "sync mon wiki" | wiki-update |
| "statut" / "tableau de bord wiki" / "what's the status" | wiki-status |
| "vérifie mon wiki" / "lint" / "liens cassés" / "wiki health" | wiki-lint |
| "qu'est-ce que X" / "trouve" / "que sais-je sur" / any question | wiki-query |
| "fais-moi un briefing sur" / "un exposé complet sur" / "brief me on X" / "narrate" | wiki-narrate |
| "reparts de zéro" / "rebuild" / "archive et reconstruit" | wiki-rebuild |
| "tisse les liens" / "cross-link" / "connecte mon wiki" | cross-linker |
| "/ingest-url " / "add this URL to the wiki" | ingest-url |
| "/ingest-video " / "add this YouTube video" / "ingest this talk" | ingest-video |
| "ingest cette data" / "importe ce log" / "process these logs" | data-ingest |
| "fix mes tags" / "tag audit" / "normalise les tags" | tag-taxonomy |
| "export wiki" / "export graphml" / "visualise wiki" | wiki-export |
| "import wiki" / "import graph.json" / "load this markdown bundle" | wiki-import |
| "make a skill from my wiki" / "turn these notes into a skill" | vault-skill-factory |
| "/wiki-history-ingest claude|codex|hermes|openclaw|copilot|pi" | wiki-history-ingest |
| "importe mon historique Claude" / "mine my conversations" | claude-history-ingest |
| "importe mon historique Codex" / "process my Codex sessions" | codex-history-ingest |
| "importe mon historique Hermes" / "process my Hermes memories" | hermes-history-ingest |
| "importe mon historique OpenClaw" / "process my OpenClaw sessions" | openclaw-history-ingest |
| "importe mon historique Copilot" / "mine my Copilot sessions" / "ingest ~/.copilot" | copilot-history-ingest |
| "importe mon historique Pi" / "mine my Pi sessions" / "ingest ~/.pi" | pi-history-ingest |
| "qu'ai-je appris cette semaine" / "digest" / "résumé hebdomadaire" / "/wiki-digest" | wiki-digest |
| "recherche X" / "deep dive sur Y" / "/wiki-research [sujet]" | wiki-research |
| "/wiki-switch NOM" / "changer de vault" / "liste mes wikis" / "nouveau profil wiki" | wiki-switch |
| "sauvegarde ça" / "/wiki-capture" / "capture cette conversation" | wiki-capture |
| "/daily-update" / "sync du matin" / "rafraîchir l'index wiki" / "configurer le cron" | daily-update |
| "colorie mon graphe" / "coloriser le graphe logseq" / "couleurs par thème" | graph-colorize |
| "synthétise mon wiki" / "trouve les connexions" / "/wiki-synthesize" | wiki-synthesize |
| "déduplique mon wiki" / "fusionne les doublons" / "résolution d'identité" | wiki-dedup |
| "contexte compact" / "pack de contexte" / "/wiki-context-pack" | wiki-context-pack |
| "révise les modifications" / "staged writes" / "/wiki-stage-commit" | wiki-stage-commit |
| "crée un skill" / "nouveau skill" / "create a skill" | skill-creator |
| "valide cette implémentation" / "check my output" / "is this correct?" | impl-validator |
| "browse par outil" / "what did codex know about X" / "memory diff" | memory-bridge |
| "/wiki-claude X" / "/wiki-codex X" / "search my claude sessions for X" | wiki-agent |
| "architecture wiki" / "how does the wiki pattern work" / "show me llm-wiki" | llm-wiki |
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.
- 3d ago First seen · 129 lines · 2,042 tokens per session scan A cd640e26f788
logseq-wiki AGENTS.md is an instructions file published in the GitHub repository ystreibel/logseq-wiki (4 stars, last pushed 7d ago), licensed MIT. It adds 2,042 tokens to every session, about $0.0102 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.