joplin-llm-wiki: Skill for Codex

.agents/skills/joplin-knowledge-flow/SKILL.md

joplin-knowledge-flow is a skill for Codex from gcake119/joplin-llm-wiki. It costs 102 tokens per session (1,216 once invoked), scanned A, original, MIT.

A workflow skill for using Joplin, a note-taking app, as a local knowledge base through connected tools.

In plain words
What is it for?
Querying and brainstorming from Joplin notes, confirming captured ideas, archiving project artifacts, syncing sources or workflow notes, and compiling a wiki.
Why use it?
It gives coding agents a defined way to search notes, save useful ideas, archive project material, and keep workspace notes in sync.

Skill for Codex

Written for Codex: runs codex exec. Also seen: installed under .agents/ (shared by several agents); mentions Codex.

This is gcake119/joplin-llm-wiki's own configuration. It tells Codex 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/.agents/skills/joplin-knowledge-flow/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/gcake119/joplin-llm-wiki

Made for: Codex.

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-knowledge-flow

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/gcake119/joplin-llm-wiki/joplin-knowledge-flow"><img src="https://agentmods.dev/badge/skills/gcake119/joplin-llm-wiki/joplin-knowledge-flow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 102 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,216 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.00102 $0.01216
Opus 5 $0.00051 $0.00608
Sonnet 5 $0.00020 $0.00243
Haiku 4.5 $0.00010 $0.00122

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

Security

Grade A, and why

joplin-knowledge-flow 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.

.agents/skills/joplin-knowledge-flow/SKILL.md · 108 lines

How it starts

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

Joplin Knowledge Flow

Use the joplin-llm-wiki MCP tools as the primary interface for knowledge-flow operations in Codex or Cursor conversations.

Tool Preference

  • Use joplin_query for questions over the local wiki/ and raw/ corpus.
  • Use joplin_brainstorm for exploratory thinking that should become a brainstorming pending capture.
  • Use joplin_show_capture to inspect a pending capture without changing files.
  • Use joplin_confirm_capture to turn a pending capture into a formal note under brainstorming/chat/ or artifacts/<project>/.
  • Use joplin_suggest_archive_project before project artifact archival.
  • Use joplin_archive_project only after the user confirms the project name.
  • Use joplin_sync_sources for existing sqlite-sync modes.
  • Use joplin_sync_workflow_notes when the user edited @llm-wiki/brainstorming or @llm-wiki/artifacts in Joplin and wants those workflow notes pulled back into workspace brainstorming/ or artifacts/.
  • Use joplin_compile_wiki for existing wiki-compile or agent-compile flows.

Capture Policy Integration

When another skill has produced reusable knowledge, apply the knowledge-capture-policy rules before deciding whether to call these MCP tools. Strong signal reusable work should normally create a pending capture draft with joplin_brainstorm. Use joplin_query only when the user asks an explicit knowledge-base question that should preserve query sources. Medium signal work should ask the user whether they want a pending capture. Low signal work should not interrupt the conversation.

If MCP tools are not available in the current session, tell the user the MCP server is not loaded and ask them to reload/restart Codex or Cursor after checking the MCP configuration. Do not silently replace this workflow with ad hoc file writes.

Query And Capture

Queries should preserve the pending capture workflow:

  1. Answer with joplin_query or joplin_brainstorm.
  2. If the result includes capture_draft_id, show the id and ask whether to confirm it when the user wants a formal note.
  3. Confirm only through joplin_confirm_capture.

Read the full file on GitHub · 108 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 · 108 lines · 102 tokens per session scan A 7ef356254d38

Subscribe to this mod's changes

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

karpathy-llm-wiki

Use when building or maintaining a personal LLM-powered knowledge base. Triggers: ingesting sources into a wiki, querying wiki knowledge, linting wiki quality, 'add to wiki', 'what do I know about', or any mention of 'LLM wiki' or 'Karpathy wiki'.

Astro-Han/karpathy-llm-wiki · 67 tokens

cold-start

Day-one data bootstrapping for a new brain. Sequences the highest-leverage data sources to go from empty brain to useful brain in one session. Uses the agent host's managed connectors for safe credential handling — the agent never holds raw API keys. Covers Gmail import, calendar sync, contacts seeding, X/Twitter…

timurgaleev/memex · 97 tokens

setup

Set up memex with provisioned Postgres (RDS + pgvector), AGENTS.md injection, first import.

timurgaleev/memex · 25 tokens

eiirp

Everything In Its Right Place. The universal post-work organizer. After any significant work session, EIIRP runs a 7-phase audit: (1) inventory every output, (2) walk the filing taxonomy to decide where each lands, (3) check ontology consistency against the brain's actual shape, (4) file enriched brain pages, (5)…

timurgaleev/memex · 133 tokens

maintain

Brain health checks: back-link enforcement, citation audit, filing validation, stale info detection, orphan pages, and benchmarks. Use when asked to check brain health, run maintenance, or audit quality.

timurgaleev/memex · 44 tokens

ingest

Route content to specialized ingestion skills. Detects input type and delegates.

timurgaleev/memex · 17 tokens