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/searchgit 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.00776 |
| Opus 5 | $0.00003 | $0.00388 |
| Sonnet 5 | $0.00001 | $0.00155 |
| Haiku 4.5 | $0.00001 | $0.00078 |
Grade A, and why
search 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Search Second Brain
Search your Obsidian vault using qmd's semantic search (combines BM25 + vector similarity + reranking).
Prerequisites
qmdmust be installed and available in PATH- A qmd collection must be configured for your vault
Step 1: Check Prerequisites
Verify qmd is available:
which qmd
If not found, inform user:
qmd is not installed. Install it via:
bun add -g qmd
Then configure a collection:
qmd collection add ~/path/to/vault --name second-brain
Step 2: Load Configuration
Get the qmd collection name via sb:
npx @techpickles/sb config qmd-collection
This returns the configured collection name (defaults to second-brain if not set).
Verify the collection exists:
qmd collection list
If collection doesn't exist, inform user which collections are available and suggest adding one.
Step 3: Execute Search
If no argument provided: Ask: "What would you like to search for?"
Run the search:
qmd query "{query}" -c {collection} -n 10 --json
Step 4: Present Results
Parse JSON output. Each result has:
file:qmd://{collection}/{path}- strip theqmd://{collection}/prefixscore: 0.0-1.0 - convert to percentagetitle: document title from frontmatter or first headingsnippet: matching content with diff-like context markers (strip@@ ... @@lines)
Present results clearly:
## Search Results for "{query}"
1. **{title}** (93%)
`{path relative to vault}`
> {cleaned snippet preview, 2-3 lines max}
2. **{title}** (51%)
...
Include:
- Title from the result
- Relevance score as percentage (score × 100)
- File path relative to vault (strip
qmd://collection/prefix) - Snippet preview (clean up diff markers, show meaningful content)
If no results, suggest:
- Try different keywords
- Check if vault has been indexed (
qmd update && qmd embed)
Step 5: Offer Follow-up Actions
After showing results, offer to:
- Read a result - Use
qmd get "qmd://{collection}/{path}"to retrieve full content - Search again - Try different or refined terms
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 · 120 lines · 7 tokens per session scan A 3dba7835707a
search is a command published in the GitHub repository technicalpickles/pickled-claude-plugins (10 stars, last pushed 5d ago), licensed MIT. It adds 7 tokens to every session and 776 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.