What is process-inbox?

A workflow for moving notes from an inbox into organized PARA folders: projects, areas, resources, and archives or clippings. It adds metadata and links notes to related material.

Use it to sort Markdown notes in an Obsidian vault, choose their destination, add frontmatter, and connect them with wikilinks.

It prevents notes from staying in one unstructured pile and makes them easier to find and connect later.

process-inbox — Skill for Claude Code by JeanDiable

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 process-inbox

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/jeandiable/obsidian-claude/process-inbox/github.svg)](https://agentmods.dev/skills/jeandiable/obsidian-claude/process-inbox)

Your own site

<a href="https://agentmods.dev/skills/jeandiable/obsidian-claude/process-inbox"><img src="https://agentmods.dev/badge/skills/jeandiable/obsidian-claude/process-inbox/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/jeandiable/obsidian-claude/process-inbox"><img src="https://agentmods.dev/badge/skills/jeandiable/obsidian-claude/process-inbox.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 622 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.

Model	Per session	Once invoked
Fable 5.1	$0.00018	$0.00622
Opus 5	$0.00009	$0.00311
Sonnet 5	$0.00004	$0.00124
Haiku 4.5	$0.00002	$0.00062

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

Security

Grade A, and why

process-inbox 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 9d 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/process-inbox/SKILL.md · 72 lines

How it starts

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

Process Inbox

Move notes from 00_Inbox/ to their proper location in PARA, adding metadata and connections.

Vault Path

~~/Library/Mobile Documents/iCloud~~md~obsidian/Documents/My_note

Workflow

Step 1: List Inbox Contents

List all .md files in 00_Inbox/ (including subdirectories)
For each file, read content and determine:
- Best destination folder in PARA:
  - 20_Projects/ — if it's a project, initiative, or actionable plan
  - 30_Areas/A1-A4 — if it relates to an ongoing area of responsibility
  - 40_Resources/R1-R4 — if it's reference material
  - 50_Clippings/ — if it's external content
  - 60_Wiki/ — if it's an atomic concept definition
- Specific subfolder within the destination
- What metadata needs to be added

Present the routing plan:

Inbox items: N
Routing plan:
- "科研日记.md" → 30_Areas/A1_科研学术/
- "claude tricks.md" → 40_Resources/R1_专业知识/
- "资产配置框架.md" → 30_Areas/A4_财务管理/
...

Ask user to confirm or adjust routing.

Step 2: Process Each File

For each confirmed file:

Add/complete YAML frontmatter (title, created, modified, tags, description)
Use obsidian search query="<key terms>" to find related content → insert wikilinks
Add ## Related section immediately after YAML frontmatter (before main content)
Move file to destination folder
Move any associated attach/ files

Step 3: Report

List all moves made and new connections created.

Routing Heuristics

Research journals, experiment notes → A1_科研学术
Career plans, job materials → A2_职业发展
Self-improvement, habits → A3_个人成长
Financial plans, budgets → A4_财务管理
Technical references, tutorials → R1_专业知识
Hobby notes → R2_兴趣爱好
Book notes, summaries → R3_读书笔记
Entertainment, lifestyle → R4_生活娱乐
Web clippings, articles → 50_Clippings/
Standalone concepts → 60_Wiki/
Active initiatives with goals → 20_Projects/

Important Rules

Ask user before moving any file — never auto-move without confirmation
If a file is unclear, suggest 2-3 possible destinations and let user choose
Preserve all original content
Handle attach/ subdirectories if they exist alongside the note

Read the full file on GitHub · 72 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.

9d ago First seen · 72 lines · 18 tokens per session scan A 6e29d4c6cd01

Subscribe to this mod's changes

process-inbox is a skill published in the GitHub repository JeanDiable/obsidian-claude (2 stars, last pushed 6mo ago), licensed MIT. It adds 18 tokens to every session and 622 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.

Productivity Writing and docs

orbit-notion

Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…

nexu-io/open-design · 117 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

pinchtab-mcp

Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.

pinchtab/pinchtab · 52 tokens

process-inbox