capture

A note-taking workflow that turns a source supplied by the user into a concise note in a vault. An atomic note covers one clear idea, while a vault is a searchable collection of notes.

In plain words
What is it for?
Use it to read a source, create or find a note, place it in the inbox, and suggest related connections.
Why use it?
It searches for existing notes first, reducing duplicates and helping new information connect to what is already recorded.

Skill for Claude CodeCodex

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 skills/technicalpickles/pickled-claude-plugins/capture
Any agent
npx skills add technicalpickles/pickled-claude-plugins --skill capture
Clone the repo
git clone --depth 1 https://github.com/technicalpickles/pickled-claude-plugins

Made for: Claude Code, Codex.

Per session 201 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,676 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.00201 $0.02676
Opus 5 $0.00101 $0.01338
Sonnet 5 $0.00040 $0.00535
Haiku 4.5 $0.00020 $0.00268

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

Security

Grade A, and why

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

The scan reads SKILL.md. This mod also ships 1 executable file (evals/trigger_eval.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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/skills/capture/SKILL.md · 198 lines

How it starts

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

Capture

Write a note into the vault from a source the user hands you. One arc, five steps: search → read the primary source → create through sb → leave it in the inbox → offer connections.

This is the dominant vault interaction. Do not decompose it into separate asks; the user saying "read this and make a note" means all five steps, and the connect step in particular will not happen unless this skill runs it.

See references/note-format.md for frontmatter and body shape. See ../obsidian/references/sb-cli.md for the full sb command surface.

Step 0: Locate the vault

npx @techpickles/sb vault info
npx @techpickles/sb config qmd-collection

Read the vault's own CLAUDE.md if you haven't this session. Vault-specific policy (destinations, status vocabulary, disambiguation rules) overrides the defaults here.

Step 1: Search before creating - never skip this

Run a lex + vec pair through the qmd MCP tools, not the shell. (mcp__qmd__query is the working path; shelling out to qmd hits Metal-init failures under the sandbox.)

mcp__qmd__query
  searches: [{type: 'lex', query: '<topic terms>'},
             {type: 'vec', query: '<what the note would say>'}]
  collection: <from sb config qmd-collection>
  intent: '<why you are searching>'
  rerank: false        # CPU-only box, reranking is not worth the latency here

Show the user what already exists - path + score + snippet - before anything gets written. Often the right move is extending a note, not minting one. If a result is a strong match, say so and ask which way to go instead of quietly creating a duplicate.

When search comes up empty

A miss is not proof the note is absent. In order:

  1. Basename is the stable identity. Notes get routed between folders constantly. Search the basename across the whole vault (Glob/Grep) before concluding anything is missing.
  2. Check both inboxes. 10-19 System & Capture/11 Inbox & triage/ and 10-19 System & Capture/11 Inbox/ are separate folders with the same JD code. sb inbox list only reads the first.
  3. The note may genuinely not exist. Say that plainly and offer to start one.

Read the full file on GitHub · 198 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 · 198 lines · 201 tokens per session scan A aa3bda955740

Subscribe to this mod's changes

capture is a skill published in the GitHub repository technicalpickles/pickled-claude-plugins (10 stars, last pushed 5d ago), licensed MIT. It adds 201 tokens to every session and 2,676 once invoked, about $0.0010 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