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 instructions/technicalpickles/pickled-claude-plugins/claude-mdgit clone --depth 1 https://github.com/technicalpickles/pickled-claude-pluginsWrote 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/instructions/technicalpickles/pickled-claude-plugins/claude-md)<a href="https://agentmods.dev/instructions/technicalpickles/pickled-claude-plugins/claude-md"><img src="https://agentmods.dev/badge/instructions/technicalpickles/pickled-claude-plugins/claude-md.svg" alt="Measured on agentmods" 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 | $0.02726 | $0.02726 |
| Opus 5 | $0.01363 | $0.01363 |
| Sonnet 5 | $0.00545 | $0.00545 |
| Haiku 4.5 | $0.00273 | $0.00273 |
Grade D, and why
pickled-claude-plugins CLAUDE.md scanned grade D with 2 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 today.
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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
**Note:** `CLAUDE_PLUGIN_ROOT` is NOT set for global hooks in `~/.claude/settings.json`. Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf ~/.claude/plugins/cache/pickled-claude-plugins/{plugin}/ How it starts
The opening of the file, as written. The whole thing — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Plugins Monorepo
This repository contains Claude Code plugins for the pickled-claude-plugins.
Repository Structure
plugins/
└── {name}/ # One directory per local plugin. Canonical list: README.md "## Plugins" (generated).
Development vs Installation
Local Development
When working in this repo, plugins are at plugins/{name}/. Environment:
- Flat layout:
plugins_dir/plugin-name/hooks/ - Use
CLAUDE_PLUGIN_ROOT="$PWD/plugins/{name}"for testing
Installed (via Marketplace)
When installed, plugins are copied to cache. Environment:
- Versioned layout:
~/.claude/plugins/cache/{marketplace}/{plugin}/{version}/ CLAUDE_PLUGIN_ROOTis set automatically by Claude Code
Key Difference
Changes to local source require reinstall to take effect:
/plugin uninstall {plugin}@pickled-claude-plugins
/plugin install {plugin}@pickled-claude-plugins
# Restart Claude Code
Plugin Testing
Test tool-routing routes
# From repo root - CLAUDE_PROJECT_ROOT must match where plugin is scoped
CLAUDE_PROJECT_ROOT="$PWD" uv run --directory plugins/tool-routing tool-routing test
Verify cross-plugin route discovery
# From repo root
CLAUDE_PROJECT_ROOT="$PWD" uv run --directory plugins/tool-routing tool-routing list
# Shows routes from enabled plugins with routes.json manifests
Important: The tool-routing plugin uses manifest-driven discovery via claude plugin list --json. Local-scoped plugins are only discovered when CLAUDE_PROJECT_ROOT (or cwd) exactly matches the plugin's projectPath.
Common Issues
Plugin hooks not running after code changes
The marketplace uses "source": "directory" but still copies to cache at install time.
Fix: Reinstall and restart Claude Code.
Routes only discovered from one source
Discovery uses claude plugin list --json and filters by enabled status and project path.
Check:
# See which plugins are enabled and their project paths
claude plugin list --json | jq '.[] | select(.enabled) | {id, scope, projectPath}'
# Verify routes.json exists in cache
ls ~/.claude/plugins/cache/pickled-claude-plugins/*/latest/.claude-plugin/routes.json
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.
- today Changed · +20 lines · +804 tokens per session 9c9347033103
- 4d ago First seen · 192 lines · 1,922 tokens per session scan D 880fac77b54f
pickled-claude-plugins CLAUDE.md is an instructions file published in the GitHub repository technicalpickles/pickled-claude-plugins (10 stars, last pushed today), licensed MIT. It adds 2,726 tokens to every session, about $0.0136 per session on Opus 5. A static security scan graded it D with 2 findings (reads agent configuration directories, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
superpowers-graph CLAUDE.md
Claude Code instructions for RonMizrahi/superpowers-graph, covering superpowers-graph — repository guide, sources of truth, changing the graph — the eval ships with the change and rules that are not obvious from the code.
workflows-mcp-server AGENTS.md
Instructions for cyanheads/workflows-mcp-server, covering agent protocol, what's next?, core rules, patterns and tool.
cf-multiworker-starter-kit AGENTS.md
AGENTS.md instructions for firtoz/cf-multiworker-starter-kit, covering agent instructions, read first (by task), cloud agents, one-liner defaults and creating new skills.
pedal
Unified skill for managing the entire PEDAL cycle. PEDAL is a workspace-level workflow modeled after the traditional PDCA cycle. Supports 'Plan → Engineering → Do → Analyze → Learn' workflow with automatic phase progression. Use proactively when user mentions PEDAL cycle, planning, engineering documents, gap analysis…
my-claude-skills CLAUDE.md
Instructions for brody-0125/my-claude-skills, covering claude code skills repository, validation commands, sub-kopring-engineer: kotlin/java 코드 컨벤션 검증, numerical: 수치 연산 코드 검증 and sub-test-engineer: 문서 일관성 검증.
MCPs copilot-instructions.md
Copilot instructions for AceDataCloud/MCPs, covering copilot sync instructions for acedatacloud mcps, repository structure, source of truth, what to sync and rules.