process

A command for processing unorganized notes in an inbox folder. It adds information such as topic, note type, tags, and description, then moves ready notes into the next folder.

In plain words
What is it for?
Use it to classify inbox notes, detect multiple topics, route reasoning to a thinking folder, and prepare notes for the rest of the vault.
Why use it?
It turns raw captures into consistently labeled notes and flags material that is better kept as ongoing thinking or research.

Command for Claude Code

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.

agentmods
npx agentmods add commands/superuser-pal/awesome-second-brain/process
Clone the repo
git clone --depth 1 https://github.com/superuser-pal/awesome-second-brain

Made for: Claude Code.

Per session 44 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,158 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00044 $0.01158
Opus 5 $0.00022 $0.00579
Sonnet 5 $0.00009 $0.00232
Haiku 4.5 $0.00004 $0.00116

Measured 2d ago against content hash 6a3ff103d9f7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

process 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 2d 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.

.claude/commands/core/process.md · 105 lines

How it starts

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

Process all unprocessed notes in inbox/raw/, then scan thinking/ for any notes ready to promote.

Part 1: inbox/raw/

For each .md file in inbox/raw/:

  1. Read the content and analyze what it contains.

  2. Detect domain — Check if content matches any registered domain in CLAUDE.md:

    • High confidence (obvious match): suggest the domain
    • Low confidence (unclear): ask the user to choose or create a new domain
    • If no domains exist yet, ask user to create one first via the create-domain skill
  3. Classify note type — Determine the type field:

    • concept, decision, reference, meeting, idea, note, belief, frame, lesson, model, goal, plan, research
  4. Check for thinking content — If the content is primarily reasoning, a scratchpad, an open question, or ongoing research, offer to route to thinking/ instead of inbox/ready/:

    • "This looks like a thinking note (reasoning/research/scratchpad). Move to thinking/ with status: thinking?"
    • If yes: git mv inbox/raw/[file] thinking/[YYYY-MM-DD-topic].md, set status: thinking, skip remaining steps for this file
    • If no: continue to step 5
  5. Check for multi-topic content — Scan for structural signals that the note covers 3+ independently page-worthy topics (each self-contained and useful on its own without the others):

    • 3+ H2 (##) sections with clearly different subjects
    • [fact]/[idea] blocks that are clearly unrelated and independently meaningful

    Only flag if topics are genuinely separable — not if sections are tightly related and better understood together. If detected, add a visible notice:

    "This note covers [N] independently page-worthy topics. When you run /distribute, you'll be offered to split it into separate pages."

  6. Generate frontmatter — Add full YAML frontmatter:

    ---
    name: "[descriptive_kebab-case_name]"
    domain: "[detected-domain]"
    origin: braindump
    type: "[detected-type]"
    status: unprocessed
    description: "[~150 char summary]"
    tags: []
    date: "[original date from raw note, quoted string]"
    created: "[original date from raw note, quoted string]"
    last_updated: "[today, quoted string]"
    ---
    
  7. Preserve original source — Before any transformation, capture the entire raw content in a collapsible callout at the bottom of the note:

    > [!quote]- Original Source
    > [verbatim raw text, exactly as captured, no formatting changes]
    

    The processed/transformed content lives above this callout as the main body. The callout is collapsed by default so it doesn't clutter reading, but the original is always available for reference.

  8. Preserve observation categories — Keep any [fact], [idea], [decision], etc. syntax from the raw capture.

  9. Move to inbox/ready/ — Use a two-step process to move and update status: 9a. Move the file: bash mv inbox/raw/[filename] inbox/ready/[filename] (Use plain mv for untracked files, git mv if tracked) 9b. Edit inbox/ready/[filename]: change status: unprocessedstatus: ready

  10. Update brain/QUEUE.md — Record or update the note's processing state:

    • If the note path is not already in the table: append a new row with Stage ready, today's date, and any relevant notes.
    • If the note path already exists (e.g., it was previously in the queue as raw): update the Stage field to ready and update Last touched.
    | inbox/ready/[filename] | ready | YYYY-MM-DD | — |
    
  11. Report for each note:

    • Original filename
    • Detected domain + type
    • Generated description
    • New location in inbox/ready/ (or thinking/ if rerouted)

Read the full file on GitHub · 105 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. 2d ago First seen · 105 lines · 44 tokens per session scan A 6a3ff103d9f7

Subscribe to this mod's changes

process is a command published in the GitHub repository superuser-pal/awesome-second-brain (14 stars, last pushed 4mo ago), licensed MIT. It adds 44 tokens to every session and 1,158 once invoked, about $0.0002 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-30.

Related

Other commands, from other repositories

canvas

AI-orchestrated visual canvas production — create, populate, layout, present, generate, and export Obsidian canvases.

AgriciDaniel/claude-canvas · 25 tokens

ingest

Ingest a source (URL/file/text) into Raw Sources + compile 1015 Wiki pages, with mandatory user-purpose gate and mothership cross-linking.

johnfkoo951/cmds-llm-wiki · 33 tokens

audit

Audit the whole Wiki vault against 3 knowledge-integrity criteria — eligibility coverage, MOC-cluster consistency, confidence calibration. Produces a vault health report and queues high-priority pages for /verify.

johnfkoo951/cmds-llm-wiki · 41 tokens

verify

Verify a single Wiki page against 3 knowledge-integrity criteria — eligibility, consistency, confirmability. Writes verificationStatus back to the page; flags conflicts as disputed rather than deleting them.

johnfkoo951/cmds-llm-wiki · 37 tokens

lint

Run comprehensive wiki health check — orphans, broken links, contradictions, stale pages, index sync, MOC coverage, v2/v4/v5 frontmatter coverage, Core Context freshness, and cross-vault link integrity (mainVaultRelated/mainVaultCmds).

johnfkoo951/cmds-llm-wiki · 53 tokens

onboard

Interview-based first-run setup for this LLM Wiki kit. Asks the essential questions (vault location/name, Mode A/B, mothership path, Core Context identity + reuse axes), then fills every placeholder and writes Core Context so the wiki knows you from day one. Activate when the user says "온보딩해줘", "처음 시작할게", "처음 시작"…

johnfkoo951/cmds-llm-wiki · 139 tokens