Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/technicalpickles/pickled-claude-pluginsnpx agentmods add commands/technicalpickles/pickled-claude-plugins/link-projectWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/technicalpickles/pickled-claude-plugins/link-project)<a href="https://agentmods.dev/commands/technicalpickles/pickled-claude-plugins/link-project"><img src="https://agentmods.dev/badge/commands/technicalpickles/pickled-claude-plugins/link-project/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/technicalpickles/pickled-claude-plugins/link-project"><img src="https://agentmods.dev/badge/commands/technicalpickles/pickled-claude-plugins/link-project.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00009 | $0.00798 |
| Opus 5.5 | $0.00004 | $0.00319 |
| Sonnet 5.5 | $0.00002 | $0.00160 |
| Haiku 4.5 | $0.00001 | $0.00080 |
Grade A, and why
link-project 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 1mo 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Link Project to Vault
Create a symlink from current repo to a folder in your vault.
Step 1: Check Configuration
Read ~/.claude/second-brain.md for vault names and paths.
If missing:
Second brain not configured. Run /second-brain:setup first.
Use the symlink path ~/.claude/vaults/{name} to access vaults.
Step 2: Select Vault
If multiple vaults configured, ask which one:
Use AskUserQuestion: Question: "Which vault should this project connect to?" Options: List configured vaults
If only one vault, use it automatically.
Step 3: Browse Vault Structure
Show top-level folders in vault:
ls -d {vault}/*/ | head -10
Ask user to select or specify path:
"Which folder in your vault? (or type a path)"
Options:
- Areas/
- Projects/
- Resources/
- (type custom path)
May need to drill down into subfolders.
Step 4: Determine Local Path
Suggest default based on vault folder name:
Vault folder: Areas/gusto/ASYNC/
Suggested local path: docs/ASYNC/
Use this path? [Yes] [Custom path]
Step 5: Create Symlink
# Create parent directory if needed
mkdir -p {local_parent}
# Create symlink
ln -s "{vault_path}" "{local_path}"
# Verify
ls -la "{local_path}"
Step 6: Write Local Config
Create .claude/second-brain.local.md:
# Second Brain Connection
Vault: {vault_name}
Symlinks:
- {local_path}/ → {vault_relative_path}/
If file exists, append new symlink to list.
Step 7: Check Gitignore
git check-ignore .claude/second-brain.local.md
If not ignored (exit code 1):
⚠ .claude/second-brain.local.md is not gitignored.
This file contains host-specific paths and shouldn't be committed.
Options:
1. Add to .git/info/exclude (this repo only)
2. Add to global gitignore (~/.config/git/ignore)
3. Skip (I'll handle it)
If option 1:
echo ".claude/second-brain.local.md" >> .git/info/exclude
If option 2:
mkdir -p ~/.config/git
echo ".claude/second-brain.local.md" >> ~/.config/git/ignore
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.
- 1mo ago First seen · 151 lines · 9 tokens per session scan A fb621c178bbc
link-project is a command published in the GitHub repository technicalpickles/pickled-claude-plugins (11 stars, last pushed yesterday), licensed MIT. It adds 9 tokens to every session and 798 once invoked, about $0.0000 per session on Opus 5.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-propose
Propose a new change - create it and generate all artifacts in one step.
OPSX: Apply
Implement tasks from an OpenSpec change (Experimental).
OPSX: Propose
Propose a new change - create it and generate all artifacts in one step.
/opsx-archive
Archive a completed change in the experimental workflow.
/opsx-apply
Implement tasks from an OpenSpec change (Experimental).
OPSX: Archive
Archive a completed change in the experimental workflow.