logseq

A connection to a local Logseq graph, which is a folder of linked notes and task pages stored as files. It can work with notes and TODOs, check their consistency, reorganize pages, and bring in notes from an Obsidian vault.

In plain words
What is it for?
Use it to add journal entries or page notes, answer questions from the graph, find consistency problems, merge or restructure pages, and import Obsidian notes.
Why use it?
It helps keep a file-based knowledge base organized and makes information in the graph easier to capture and find. It can use Logseq's local interface when available and fall back to the files.

Plugin for Claude Code

Install

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.

Claude Code
/plugin marketplace add ericfitz/skills
agentmods
npx agentmods add plugins/ericfitz/skills/logseq
Clone the repo
git clone --depth 1 https://github.com/ericfitz/skills

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

logseq 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 yesterday.

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.

logseq/.claude-plugin/plugin.json · 7 lines

What it actually says

{
  "name": "logseq",
  "version": "1.0.0",
  "description": "Interact with a local classic (file-based) Logseq graph: capture notes/TODOs into journals or pages, answer questions from the graph, lint it for consistency, merge/restructure pages, and import notes from an Obsidian vault. Hybrid access: reads files directly, writes via the Logseq local HTTP API when the app is running, file fallback otherwise.",
  "author": { "name": "efitz" }
}
Changes

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.

  1. yesterday First seen · 7 lines scan A b98ee4b41b32

Subscribe to this mod's changes

logseq is a plugin published in the GitHub repository ericfitz/skills (2 stars, last pushed 9d ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.