connect

A command that finds related notes in a vault and links them together using semantic search, which looks for similar meaning rather than only matching words.

In plain words
What is it for?
Use it to connect one note to related notes or to discover connection opportunities across the vault.
Why use it?
It helps reveal relationships between notes that may use different wording or were created at different times.

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/connect
Clone the repo
git clone --depth 1 https://github.com/technicalpickles/pickled-claude-plugins
Per session 12 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,454 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.00012 $0.01454
Opus 5 $0.00006 $0.00727
Sonnet 5 $0.00002 $0.00291
Haiku 4.5 $0.00001 $0.00145

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

Security

Grade A, and why

connect 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/connect.md · 209 lines

How it starts

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

Connect Notes

Connect a note to related notes in your vault, or discover connection opportunities across the vault.

Step 1: Load Configuration

Read ~/.claude/second-brain.md for vault name and path.

If missing:

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

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

Load skill references:

  • second-brain:obsidian for tool mechanics
  • references/connecting.md for connection discovery algorithm

Step 2: Check Prerequisites

Follow references/connecting.md prerequisites:

which qmd

If qmd is not available:

qmd is not installed. Connection discovery requires qmd for semantic search.
Install via: bun add -g qmd
Then configure: qmd collection add ~/path/to/vault --name second-brain

Verify collection exists:

qmd collection list

Load collection name from ~/.claude/second-brain.md (qmd_collection setting). Default: second-brain.

Step 3: Determine Mode

If argument provided (note path): Go to Step 4 (Connect Specific Note) If no argument: Go to Step 7 (Connection Gardening)


Connect Specific Note

Step 4: Load Target Note

Resolve the path. Accept:

  • Vault-relative path: Areas/gusto/202501121430 kafka-consumer-groups.md
  • Absolute path: ~/Vaults/pickled-knowledge/.../file.md
  • Just the filename: 202501121430 kafka-consumer-groups.md (search for it)

If just a filename, find it:

find "{vault}" -name "{filename}" -type f 2>/dev/null

Read the note content.

If note not found:

Note not found: {path}
Check the path and try again.

Step 5: Run Connection Discovery

Follow the full references/connecting.md algorithm:

  1. Extract query terms from the note's title and body
  2. Run qmd query "{terms}" -c {collection} -n 15 --json
  3. Filter noise (self, already-linked, low-relevance, daily notes)
  4. Enrich candidates (check for See Also, Related, TK sections)
  5. Rank by connection value
  6. Present candidates for multi-select

Read the full file on GitHub · 209 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 · 209 lines · 12 tokens per session scan A 43901ced9a74

Subscribe to this mod's changes

connect is a command published in the GitHub repository technicalpickles/pickled-claude-plugins (10 stars, last pushed 4d ago), licensed MIT. It adds 12 tokens to every session and 1,454 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.