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.
npx agentmods add commands/technicalpickles/pickled-claude-plugins/insightgit clone --depth 1 https://github.com/technicalpickles/pickled-claude-pluginsWhat 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 | $0.00009 | $0.01084 |
| Opus 5 | $0.00005 | $0.00542 |
| Sonnet 5 | $0.00002 | $0.00217 |
| Haiku 4.5 | $0.00001 | $0.00108 |
Grade A, and why
insight 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.
How it starts
The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Capture Insight
Capture an insight from the current conversation to your Obsidian vault inbox.
This command captures raw insights quickly. Processing, routing, and connection discovery happen later via /second-brain:process-inbox.
Step 1: Load Configuration
Load configuration using sb CLI:
npx @techpickles/sb config default # Get default vault name
npx @techpickles/sb config vaults # List all configured vaults
If sb is not available, inform user:
sb CLI is required but not available. Install Node.js and npm, then try again.
Or install globally for faster execution: npm i -g @techpickles/sb
If no vaults are configured, inform user:
Second brain not configured. Run /second-brain:setup first.
Use the symlink path ~/.claude/vaults/{name} to access the vault for reading CLAUDE.md (e.g., ~/.claude/vaults/primary).
Read vault's CLAUDE.md for structure rules.
Load skill references:
second-brain:obsidianfor tool mechanicsreferences/sb-cli.mdfor sb invocation detailsreferences/zettelkasten.mdfor naming
Step 2: Identify the Insight
If argument provided: Use the argument as the insight to capture.
If no argument: Ask: "What insight would you like to capture?"
Also review recent conversation context to suggest what might be worth capturing.
Step 3: Create or Append to Session Notes
Session notes files collect all insights from a conversation in one place, with cheap metadata attached at capture time.
Check if session file already exists in this conversation.
If this is the first /insight command in this conversation:
- Create a new session notes file using sb CLI:
npx @techpickles/sb note create \
--source auto \
--title "{session context}"
Generate the title from conversation context: repo name, current branch, bean ID if available, and what you're working on (e.g., "Debugging auth timeout in zenpayroll").
The file is created with frontmatter. Read the created file to preserve the exact frontmatter sb wrote.
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.
- 2d ago First seen · 138 lines · 9 tokens per session scan A 98f53a378b01
insight is a command published in the GitHub repository technicalpickles/pickled-claude-plugins (10 stars, last pushed 5d ago), licensed MIT. It adds 9 tokens to every session and 1,084 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.
Other commands, from other repositories
OPSX: Onboard
Guided onboarding - walk through a complete OpenSpec workflow cycle with narration.
OPSX: Bulk Archive
Archive multiple completed changes at once.
OPSX: Explore
Enter explore mode - think through ideas, investigate problems, clarify requirements.
OPSX: Verify
Verify implementation matches change artifacts before archiving.
OPSX: Apply
Implement tasks from an OpenSpec change (Experimental).
OPSX: Archive
Archive a completed change in the experimental workflow.