organize-para

organize-para is a skill for Claude Code from JeanDiable/obsidian-claude. It costs 28 tokens per session (799 once invoked), scanned A, original, MIT.

A batch organizer for PARA notes in an Obsidian vault. PARA is a method that groups notes into Projects, Areas, Resources, and Archives.

In plain words
What is it for?
Use it to scan selected PARA folders, add or repair metadata, create links between notes, and organize connections.
Why use it?
It helps add missing note details and links between related files, while showing a summary and asking for confirmation before changes.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions subagents.

Part of the obsidian-claude plugin — 19 skills shipped together

Good fit Use it to scan selected PARA folders, add or repair metadata, create links between notes, and organize connections.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jeandiable/obsidian-claude/organize-para
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.

Any agent
npx skills add JeanDiable/obsidian-claude --skill organize-para
Clone the repo
git clone --depth 1 https://github.com/JeanDiable/obsidian-claude

Made for: Claude Code.

Or install obsidian-claude, the plugin that ships this one along with the rest of its 19 skills.

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 organize-para

README.md
[![agentmods](https://agentmods.dev/badge/skills/jeandiable/obsidian-claude/organize-para/github.svg)](https://agentmods.dev/skills/jeandiable/obsidian-claude/organize-para)
Your own site
<a href="https://agentmods.dev/skills/jeandiable/obsidian-claude/organize-para"><img src="https://agentmods.dev/badge/skills/jeandiable/obsidian-claude/organize-para/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 organize-para

Your own site · 80×15
<a href="https://agentmods.dev/skills/jeandiable/obsidian-claude/organize-para"><img src="https://agentmods.dev/badge/skills/jeandiable/obsidian-claude/organize-para.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 799 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.00028 $0.00799
Opus 5 $0.00014 $0.00400
Sonnet 5 $0.00006 $0.00160
Haiku 4.5 $0.00003 $0.00080

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

Security

Grade A, and why

organize-para 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 12d 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.

skills/organize-para/SKILL.md · 94 lines

How it starts

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

Organize PARA

Batch process all files in PARA folders (20_Projects, 30_Areas, 40_Resources, 80_Archive) to add metadata and create interconnections.

Vault Path

/Library/Mobile Documents/iCloudmd~obsidian/Documents/My_note

Workflow

Phase 1: Scan & Plan

  1. List all .md files in these vault folders:

    • 20_Projects/
    • 30_Areas/ (recursively including A1-A4 subfolders)
    • 40_Resources/ (recursively including R1-R4 subfolders)
    • 80_Archive/
  2. For each file, check if it has YAML frontmatter. Categorize into:

    • Missing metadata: No frontmatter at all
    • Partial metadata: Has frontmatter but missing required fields (title, created, modified, tags, description)
    • Complete: Has all required fields
  3. Present a summary to the user:

    Files scanned: N
    Missing metadata: X
    Partial metadata: Y
    Complete: Z
    
  4. Ask user to confirm before proceeding.

Phase 2: Add/Fix Metadata

For each file needing metadata work:

  1. Read the full file content
  2. Generate appropriate metadata:
    • title: Extract from first heading or filename
    • created: Use file creation date if available, or today's date
    • modified: Today's date
    • tags: Generate 1-5 relevant tags from content analysis
    • description: Write a 1-2 sentence summary of the content
    • completed: (Projects only) Determine from content if project is done
  3. Add or update YAML frontmatter at the top of the file
  4. If file already has partial frontmatter, preserve existing correct values and fill in missing ones

Phase 3: Build Connections

For each processed file:

  1. Extract key concepts, terms, and topics from the content
  2. Search the entire vault (PARA + 50_Clippings + 60_Wiki) for files with related content:
    • Use obsidian search query="<term>" to find matching files
    • Check existing tags for overlap
    • Look for files in the same domain/area
  3. Insert [[wikilinks]] inline in the text where concepts naturally appear and a matching file exists
  4. Add or update a ## Related section immediately after the YAML frontmatter (before the main content):
    ---
    (frontmatter)
    ---
    
    ## Related
    - [[RelatedFile1]] — brief description of relationship
    - [[RelatedFile2]] — brief description of relationship
    
    (rest of file content)
    
  5. If linking to a 60_Wiki entry, also update that wiki entry's Related section to point back

Read the full file on GitHub · 94 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. 12d ago First seen · 94 lines · 28 tokens per session scan A 5da7699beea2

Subscribe to this mod's changes

organize-para is a skill published in the GitHub repository JeanDiable/obsidian-claude (2 stars, last pushed 6mo ago), licensed MIT. It adds 28 tokens to every session and 799 once invoked, about $0.0001 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

media-ingest

Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.

garrytan/gbrain · 52 tokens

mem0-oss-to-platform

Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…

mem0ai/mem0 · 273 tokens

Cortex

Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…

danielmiessler/LifeOS · 196 tokens

memory

Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.

opensquilla/opensquilla · 44 tokens

ha-data-stores

Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…

shiwenwen/hope-agent · 115 tokens

establishing-project-context

Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.

GanyuanRan/Aegis · 45 tokens