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.
/plugin marketplace add technicalpickles/pickled-claude-pluginsnpx agentmods add plugins/technicalpickles/pickled-claude-plugins/buildkitegit clone --depth 1 https://github.com/technicalpickles/pickled-claude-pluginsGrade A, and why
buildkite 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 yesterday.
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.
What it actually says
{
"name": "buildkite",
"description": "Buildkite CI tools: build investigation, pipeline development, and tool preference enforcement",
"author": {
"name": "Josh Nichols",
"email": "[email protected]"
},
"repository": "https://github.com/technicalpickles/pickled-claude-plugins",
"license": "MIT"
}
What ships with it
1 file beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 11 lines scan A 6655365ee101
buildkite is a plugin published in the GitHub repository technicalpickles/pickled-claude-plugins (10 stars, last pushed 4d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
qiushi-skill
Qiushi Skill: methodology skills for AI agents guided by seeking truth from facts, with Claude Code, Cursor, OpenClaw, Codex, OpenCode, and Hermes guidance.
kiln
Multi-model software creation pipeline. A conversation becomes running, tested software — an interactive brainstorm, then an autonomous build: GPT-5.6 writes the code, Claude shapes the plans and interfaces, and each family inspects the work of the other.
kit
Spec-driven Claude Code workflow with verification pipeline. Hooks, slash commands, and verification subagents.
bengous-plugins
Personal Claude Code plugins: git workflows, code quality, agent orchestration, and plugin tooling.
phd-deepread-workflow
Transform academic PDFs into structured literature notes and critical-thinking canvases for Obsidian.
dw-solo-extras
Off-loop skills for the solo lane — reached for beside the loop, not on the way from shape to ship. Four today: compact the live session into a handoff the next context window resumes from, mid-task; walk the backlog entry by entry, dropping what is stale and doing what is cheap; cut the AI tells out of the text a…