joplin-llm-wiki: Skill for Codex

.cursor/skills/joplin-brain-dev/SKILL.md

joplin-brain-dev is a skill for Codex, Cursor from gcake119/joplin-llm-wiki. It costs 70 tokens per session (2,179 once invoked), scanned A, original, MIT.

Development instructions for a Joplin-based knowledge system that exports notes from SQLite into Markdown and can compile them into other knowledge layers. SQLite is a small database stored in a file.

In plain words
What is it for?
Use them when changing SQLite synchronization, wiki or agent compilation, configuration loading, embedded test configuration, snapshots, or health-monitoring screens.
Why use it?
They define which exported files are read-only, when synchronization and compilation run, and how scheduled checks should behave.

Skill for CodexCursor

Written for Codex and Cursor: runs codex exec, but also installed under .cursor/. Also seen: mentions Codex.

This is gcake119/joplin-llm-wiki's own configuration. It tells Codex and Cursor how to work on joplin-llm-wiki itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything joplin-llm-wiki configures →

Reuse

Borrowing it

Nothing to install: this file belongs to gcake119/joplin-llm-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.

Copy the file
curl -O https://raw.githubusercontent.com/gcake119/joplin-llm-wiki/main/.cursor/skills/joplin-brain-dev/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/gcake119/joplin-llm-wiki

Made for: Codex, Cursor.

Wrote 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.

agentmods badge for joplin-brain-dev

README.md
[![agentmods](https://agentmods.dev/badge/skills/gcake119/joplin-llm-wiki/joplin-brain-dev/github.svg)](https://agentmods.dev/skills/gcake119/joplin-llm-wiki/joplin-brain-dev)
Your own site
<a href="https://agentmods.dev/skills/gcake119/joplin-llm-wiki/joplin-brain-dev"><img src="https://agentmods.dev/badge/skills/gcake119/joplin-llm-wiki/joplin-brain-dev/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.

agentmods 80×15 button for joplin-brain-dev

Your own site · 80×15
<a href="https://agentmods.dev/skills/gcake119/joplin-llm-wiki/joplin-brain-dev"><img src="https://agentmods.dev/badge/skills/gcake119/joplin-llm-wiki/joplin-brain-dev.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 70 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,179 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00070 $0.02179
Opus 5 $0.00035 $0.01090
Sonnet 5 $0.00014 $0.00436
Haiku 4.5 $0.00007 $0.00218

Measured 11d ago against content hash ec59eb82afd0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

joplin-brain-dev 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.

.cursor/skills/joplin-brain-dev/SKILL.md · 97 lines

How it starts

The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.

joplin-llm-wiki 開發慣例

在修改 sqlite-syncwiki-compileagent-compile、設定載入、或 test/**/*.test.js 內嵌 config.yaml 時遵守下列規則。

知識流與模型邊界

  • 本 repo 部分採用 gatelynch/llm-knowledge-base 的四層知識流:raw/ 對應 raw/wiki/ 對應 wiki/,並保留 brainstorming/artifacts/
  • raw/ 是 Joplin SQLite mirror/export 產物,預設視為唯讀證據;不要手動放入長期維護內容。
  • Notebook 篩選匯出使用 raw/<joined-notebook-slug>/<safe-title>.md。巢狀筆記本以 - 串接,例如 工作/專案A/會議工作-專案A-會議
  • sqlite-sync 正常模式匯出後會比對 snapshot,只有 raw 變更才依 joplin_sqlite_sync.pipeline.compile_mode 觸發 wiki 層同步:local 執行 wiki-compileagent 執行 agent-compileoff 不編譯。第一次非 dry-run 只建立 baseline;--export-only 會更新 raw 與 snapshot state 但不編譯;--snapshot-only 只掃現有 raw/ 建立 baseline,不開 SQLite、不刪檔、不編譯。舊 run_wiki_compile 只作為未設定 compile_mode 時的 fallback。
  • sqlite-sync 的自動檢查是輪詢,不是檔案 watcher。若要常駐定時檢查,設定 joplin_sqlite_sync.schedule.every_seconds 或 CLI --every <seconds>;若改由 launchd/cron 重複啟動單輪命令,讓 every_seconds 保持 null,避免同時使用內外兩層排程。
  • sqlite-sync summary 欄位要保持可觀測:raw_changedchange_detectionchanged_filescompile_modecompile_triggered。Health GUI 主要 tabs 應覆蓋 Health、Config、Notebooks、Pipeline、Query、Lint、LaunchAgent,並透過固定 IPC handler 執行 Query/Lint/snapshot-only。
  • 編譯輸出只能使用 wiki/summaries/*.mdwiki/concepts/*.mdwiki/indexes/All-Sources.mdwiki/indexes/All-Concepts.md;三個分類底下不得建立子資料夾。summaries 是每個來源一份摘要,concepts 是概念條目並交叉引用 summaries/concepts,indexes 是固定入口。
  • query 預設使用 --source-scope=knowledge:優先讀 wiki/,必要時補 raw/ 原始素材;可用 --source-scope=wiki|raw 明確限制。成功回答不直接 file-back,會先建立 pending capture,確認後才寫 brainstorming/chat/artifacts/projects/<project>/askindexwatch、RAG/Chroma/embedding vector 管線已移除。
  • 人可讀的知識管理輸出使用繁體中文;技術名詞、source path、filename 可保留原文。
  • 模型分流:
    • 本地預設是 wiki-compile + Ollama。
    • Codex 月訂閱路線是 agent-compile + 本機已登入的 codex exec,不使用 OpenAI API key,也不等同 API 額度。
    • 兩條管路預設都掃完整個 raw/ 筆記庫;--batch=true 才是 10-15 頁單批次 fallback。
    • OpenAI API provider 目前未實作。

本機小模型(config.yaml.example 對齊值)

Read the full file on GitHub · 97 lines

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. 11d ago First seen · 97 lines · 70 tokens per session scan A ec59eb82afd0

Subscribe to this mod's changes

joplin-brain-dev is a skill published in the GitHub repository gcake119/joplin-llm-wiki (2 stars, last pushed 3mo ago), licensed MIT. It adds 70 tokens to every session and 2,179 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

design-mcp-server

Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.

cyanheads/obsidian-mcp-server · 62 tokens

api-canvas

DataCanvas primitive reference — a Tier 3 SQL/analytical workspace for tabular MCP servers, backed by DuckDB. Use when registering tables from upstream APIs, running ad-hoc SQL across them, and exporting results. Covers the acquire → register → query → export flow, per-table TTL, the token-sharing pattern for…

cyanheads/obsidian-mcp-server · 85 tokens

api-testing

Testing patterns for MCP tool/resource handlers using createMockContext and Vitest. Covers mock context options, handler testing, McpError assertions, format testing, Vitest config setup, and test isolation conventions.

cyanheads/obsidian-mcp-server · 46 tokens

release-and-publish

Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…

cyanheads/obsidian-mcp-server · 155 tokens

api-telemetry

Catalog of OpenTelemetry instrumentation built into framework @cyanheads/mcp-ts-core — spans, metrics, completion logs, env config, runtime caveats, custom instrumentation patterns, and cardinality rules. Use when enabling OTel export, adding custom spans or metrics in services, debugging missing telemetry, looking up…

cyanheads/obsidian-mcp-server · 85 tokens

maintenance

Investigate, adopt, and verify dependency updates — with special handling for @cyanheads/mcp-ts-core. Captures what changed, understands why, cross-references against the codebase, adopts framework improvements, syncs project skills, and runs final checks. Supports two entry modes: run the full flow end-to-end, or…

cyanheads/obsidian-mcp-server · 75 tokens