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 skills add sohampatwardhan/Agentic-Joplin --skill joplin-organizinggit clone --depth 1 https://github.com/sohampatwardhan/Agentic-JoplinWrote 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/skills/sohampatwardhan/agentic-joplin/joplin-organizing)<a href="https://agentmods.dev/skills/sohampatwardhan/agentic-joplin/joplin-organizing"><img src="https://agentmods.dev/badge/skills/sohampatwardhan/agentic-joplin/joplin-organizing/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.
<a href="https://agentmods.dev/skills/sohampatwardhan/agentic-joplin/joplin-organizing"><img src="https://agentmods.dev/badge/skills/sohampatwardhan/agentic-joplin/joplin-organizing.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00033 | $0.00436 |
| Opus 5.5 | $0.00013 | $0.00174 |
| Sonnet 5.5 | $0.00007 | $0.00087 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
joplin-organizing 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 5d 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.
What it actually says
Organizing a Joplin workspace
See the using-joplin skill for the connection check and shared conventions.
Survey first
Call list_notebooks (use the nested tree) and list_tags to understand the current
structure before changing anything. Confirm the intended end state with the user for anything
sweeping.
Notebooks
- Rename or move:
update_notebookwithtitle(rename) and/orparent_id(move under a new parent; a top-level notebook has an emptyparent_id). - Create structure:
create_notebookwithparent_idto build nested notebooks.
Tags
- Attach/detach with
tag_note/untag_note. create_tag,update_tag(rename),delete_tagmanage the tag vocabulary itself.
Cleanup — be careful
delete_note/delete_notebooktrash by default; only passpermanent: trueafter the user explicitly confirms, since it can't be undone. Prefer trashing.- For bulk operations, enumerate with
list_notes(by notebook or tag) and act per-item. Watch thetruncatedflag — if the list was capped, process in narrower batches so you don't miss items.
Notes
- Moving a notebook moves all its notes and sub-notebooks with it.
- Organizing doesn't change note bodies. If merging notes means combining bodies, keep any
Mermaid or math blocks intact (see "Diagrams and math" in
using-joplin). - When deduplicating or merging notebooks, move notes to the target first, verify, then delete the now-empty source (trashed, not permanent, unless confirmed).
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.
- 5d ago Changed · +5 lines 502f7f4e8d24
- 2mo ago First seen · 40 lines · 33 tokens per session scan A 3f1d9939fd58
joplin-organizing is a skill published in the GitHub repository sohampatwardhan/Agentic-Joplin (0 stars, last pushed 6d ago), licensed MIT. It adds 33 tokens to every session and 436 once invoked, about $0.0001 per session on Opus 5.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-09-01.
joplin-organizing compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| joplin-organizingsohampatwardhan/Agentic-Joplin | Skill | 0 | 6d ago | MIT | A | 33 | Claude Code |
| joplinalondmnt/joplin-mcp | Skill | 174 | 1mo ago | MIT | B | 20 | Claude Code |
| deja-reflectvshulcz/deja-vu | Skill | 1.4k | today | MIT | A | 49 | Claude Code |
| specimen-authoringdylanroscover/Embody | Skill | 213 | 3d ago | MIT | A | 38 | Claude Code |
| externalize-operatordylanroscover/Embody | Skill | 213 | 3d ago | MIT | A | 22 | Claude Code |
| multi-instancedylanroscover/Embody | Skill | 213 | 3d ago | MIT | A | 23 | Claude Code |
| agent-desktop-windowsopenwong2kim/wmux | Skill | 447 | today | MIT | A | 119 | Claude Code, Codex |