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/setupgit 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.00007 | $0.01160 |
| Opus 5 | $0.00003 | $0.00580 |
| Sonnet 5 | $0.00001 | $0.00232 |
| Haiku 4.5 | $0.00001 | $0.00116 |
Grade A, and why
setup 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Second Brain Setup
Configure vault paths and scaffold vault CLAUDE.md.
For sb CLI details, see references/sb-cli.md.
Step 1: Check Existing Config
Check if vaults are already configured:
npx @techpickles/sb config vaults
This returns JSON with configured 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 vaults exist, show current and ask:
- Add another vault?
- Reconfigure existing vault?
- Cancel
Step 2: Get Vault Path
Ask user for vault path. No assumed locations, just ask directly:
"Where is your Obsidian vault located? (full path)"
Step 3: Validate Vault
Check the path exists:
ls -d "{path}" 2>/dev/null
Parse .obsidian config (if present):
npx @techpickles/sb vault obsidian --path "{path}"
This outputs JSON with:
- Daily notes folder and template
- Templates folder
- Inbox/new notes folder
- Attachments folder
If .obsidian/ missing, sb will indicate this in the output:
- Might not be an Obsidian vault
- Offer to continue anyway (for plain markdown repos)
- Or user can open folder in Obsidian first to initialize
Step 4: Confirm Settings
Show detected settings from the sb output:
Detected from .obsidian/:
- Daily notes: Fleeting/ (template: Templates/daily)
- Templates: Templates/
- Inbox: 📫 Inbox/
- Attachments: 🖇 Attachments/
Does this look right? [Yes] [Adjust]
Step 5: Name the Vault
Ask for short identifier:
"What should I call this vault? (e.g., primary, work, personal)"
Suggest "primary" if this is the first vault.
Step 6: Initialize Configuration
Create or update ~/.claude/second-brain.md:
npx @techpickles/sb init --name "{name}" --path "{path}"
Add --scaffold flag if user wants to create vault CLAUDE.md:
npx @techpickles/sb init --name "{name}" --path "{path}" --scaffold
This command:
- Writes the vault configuration to
~/.claude/second-brain.md - Optionally creates
{vault}/CLAUDE.mdwith detected settings
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 · 174 lines · 7 tokens per session scan A 73d926cd7dd3
setup is a command published in the GitHub repository technicalpickles/pickled-claude-plugins (10 stars, last pushed 4d ago), licensed MIT. It adds 7 tokens to every session and 1,160 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: Archive
Archive a completed change in the experimental workflow.
OPSX: Continue
Continue working on a change - create the next artifact (Experimental).