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/copilot-instructionsgit 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/instructions/ystreibel/logseq-wiki/copilot-instructions)<a href="https://agentmods.dev/instructions/ystreibel/logseq-wiki/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/ystreibel/logseq-wiki/copilot-instructions.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 | $0.00856 | $0.00856 |
| Opus 5 | $0.00428 | $0.00428 |
| Sonnet 5 | $0.00171 | $0.00171 |
| Haiku 4.5 | $0.00086 | $0.00086 |
Grade A, and why
logseq-wiki copilot-instructions.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.
How it starts
The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Logseq Wiki — Copilot Context
This project is a skill-based framework for building and maintaining a Logseq knowledge base using AI coding agents. There are no scripts or dependencies — everything is markdown instructions that the agent executes directly.
Project Overview
- Purpose: Build and maintain a Logseq wiki using the LLM Wiki pattern (Andrej Karpathy).
- Tech Stack: Markdown only. No code, no dependencies. The AI agent IS the runtime.
- Key Config:
~/.logseq-wiki/config(or.env) containsLOGSEQ_VAULT_PATHpointing to the Logseq vault. - Skills:
.skills/contains skill folders, each with aSKILL.mddefining a workflow.
Key Concepts
- The wiki is a compiled artifact — knowledge distilled from raw sources into interconnected pages.
- Every wiki page uses Logseq property syntax:
title::,category::,tags::,summary::,sources::,created::,updated::— NEVER YAML frontmatter. - Pages are connected with Logseq
[[wiki/thème/page]]namespace links. wiki/_manifest.jsontracks all ingested sources for delta-based updates.wiki/_master-index.mdandwiki/_log.mdmust be updated after every operation.- Logseq vault sources (
pages/,journals/,assets/,logseq/) are READ ONLY.
Skills Reference
| Skill | Folder | Purpose |
|---|---|---|
| LLM Wiki | .skills/llm-wiki/ |
Core architecture, Logseq syntax, manifest format |
| Setup | .skills/wiki-setup/ |
Initialize wiki structure in vault |
| Ingest | .skills/wiki-ingest/ |
Distill documents into wiki pages |
| Update | .skills/wiki-update/ |
Sync current project knowledge into wiki |
| Status | .skills/wiki-status/ |
Audit ingestion state and delta |
| Query | .skills/wiki-query/ |
Answer questions from wiki |
| Lint | .skills/wiki-lint/ |
Find broken links, orphans, stale content |
| Rebuild | .skills/wiki-rebuild/ |
Archive and rebuild from scratch |
| Export | .skills/wiki-export/ |
Export graph to JSON, GraphML, HTML |
| Cross-Linker | .skills/cross-linker/ |
Auto-discover and insert missing wikilinks |
| Tag Taxonomy | .skills/tag-taxonomy/ |
Enforce consistent tag vocabulary |
| Ingest URL | .skills/ingest-url/ |
Fetch and distill a web page |
| Data Ingest | .skills/data-ingest/ |
Process any text data (chat exports, logs, etc.) |
| History Router | .skills/wiki-history-ingest/ |
Route /wiki-history-ingest <agent> |
| Claude History | .skills/claude-history-ingest/ |
Mine ~/.claude conversations |
| Codex History | .skills/codex-history-ingest/ |
Mine ~/.codex sessions |
| Hermes History | .skills/hermes-history-ingest/ |
Mine ~/.hermes memories |
| OpenClaw History | .skills/openclaw-history-ingest/ |
Mine ~/.openclaw sessions |
| Skill Creator | .skills/skill-creator/ |
Create new skills |
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 · 52 lines · 856 tokens per session scan A 6f7b98c04067
logseq-wiki copilot-instructions.md is an instructions file published in the GitHub repository ystreibel/logseq-wiki (4 stars, last pushed 8d ago), licensed MIT. It adds 856 tokens to every session, about $0.0043 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.