route

A command that moves notes from an inbox into the right locations in an Obsidian vault, a folder of linked Markdown notes.

In plain words
What is it for?
Use it to route a named note, review the inbox before choosing notes, or process every note in a batch.
Why use it?
It removes the need to decide manually where each incoming note belongs. It can also handle one note or all notes in the inbox.

Command

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/technicalpickles/pickled-claude-plugins/route
Clone the repo
git clone --depth 1 https://github.com/technicalpickles/pickled-claude-plugins
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,222 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.00008 $0.02222
Opus 5 $0.00004 $0.01111
Sonnet 5 $0.00002 $0.00444
Haiku 4.5 $0.00001 $0.00222

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

Security

Grade A, and why

route 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.

plugins/second-brain/commands/route.md · 309 lines

How it starts

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

Route Notes

Route notes from inbox to appropriate destinations in your vault.

Step 1: Load Configuration

Load configuration directly - don't preflight-check sb availability first:

npx @techpickles/sb config default
npx @techpickles/sb config vaults

If this fails, run ${CLAUDE_PLUGIN_ROOT}/scripts/diagnose-sb.sh for a one-shot diagnosis rather than re-deriving the checks by hand.

If no vault configured:

Second brain not configured. Run /second-brain:setup first.

Use the symlink path ~/.claude/vaults/{name} to Read vault files (e.g., ~/.claude/vaults/primary/CLAUDE.md).

Load skill references:

  • second-brain:obsidian for tool mechanics
  • references/routing.md for routing algorithm
  • references/sb-cli.md for sb command reference
  • references/routing-memory.md for routing correction format

Step 2: Identify Notes to Route

If argument is a filename: Look for that file in inbox. If not found, search vault.

If argument is "all": List all files in inbox for batch routing.

If no argument: List inbox contents and let user select:

npx @techpickles/sb inbox list

Example output:

{
  "notes": [
    {
      "filename": "202601251430 redis-session-caching.md",
      "timestamp": "202601251430",
      "title": "redis-session-caching"
    },
    {
      "filename": "202601251445 claude-code-hooks.md",
      "timestamp": "202601251445",
      "title": "claude-code-hooks"
    }
  ]
}

Present to user:

Notes in inbox:
1. 202601251430 redis-session-caching.md
2. 202601251445 claude-code-hooks.md
3. 202601251500 debugging-approach.md

Which note(s) would you like to route?

Use AskUserQuestion with multi-select to let user choose.

Step 3: Discover Vault Structure

npx @techpickles/sb vault structure

Example output:

{
  "areas": [
    "Areas/AI/agentic development",
    "Areas/tool sharpening"
  ],
  "resources": [
    "Resources/software engineering",
    "Resources/mental models"
  ],
  "projects": [
    "Projects/pickletown",
    "Projects/claude-plugins"
  ]
}

Read the full file on GitHub · 309 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 · 309 lines · 8 tokens per session scan A 66cacba1463b

Subscribe to this mod's changes

route is a command published in the GitHub repository technicalpickles/pickled-claude-plugins (10 stars, last pushed 4d ago), licensed MIT. It adds 8 tokens to every session and 2,222 once invoked, about $0.0000 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.