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 skills add technicalpickles/pickled-claude-plugins --skill setupgit 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/skills/technicalpickles/pickled-claude-plugins/setup)<a href="https://agentmods.dev/skills/technicalpickles/pickled-claude-plugins/setup"><img src="https://agentmods.dev/badge/skills/technicalpickles/pickled-claude-plugins/setup/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/skills/technicalpickles/pickled-claude-plugins/setup"><img src="https://agentmods.dev/badge/skills/technicalpickles/pickled-claude-plugins/setup.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.00083 | $0.01627 |
| Opus 5.5 | $0.00033 | $0.00651 |
| Sonnet 5.5 | $0.00017 | $0.00325 |
| Haiku 4.5 | $0.00008 | $0.00163 |
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 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup Principles
Scaffold the per-project configuration that stay-principled:grill reads. This is a prompt-driven skill, not a deterministic script. Explore, present what you found, confirm with the user, then write.
Process
1. Explore
Look at the current repo to understand its starting state. Read whatever exists; don't assume:
docs/principles.md,docs/ops-principles.md, any sibling*principles*.mdfiles at the repo root or underdocs/docs/agents/principles.md: existing config; update in place if foundCLAUDE.md(preferred) orAGENTS.mdat the repo root: does either exist? Is there already an## Agent skillssection?claude plugin list --json: istool-routinginstalled and enabled? (Affects whether Pattern C is offered.)git rev-parse --show-toplevel: used as the canonical repo root for path resolution; principles inside worktrees still live at the worktree root.
2. Present findings and ask
Summarize what's present and what's missing. Then walk the user through the four sections one at a time. Present a section, get the user's answer, then move to the next. Don't dump all sections at once.
Assume the user does not know what these terms mean. Each section starts with a short explainer (what it is, why this skill needs it, what changes if they pick differently).
Section A: Where do principles live?
Explainer: The
stay-principled:grillskill needs to know which markdown files contain your principles. Most projects have one (docs/principles.md); some split into multiple (e.g. engineering vs ops). The skill reads all of them at session start to build a working set.
Default posture: if any *principles*.md files were found during exploration, list them and ask the user to confirm or adjust. Multi-file is fine. If none were found, ask the user where their principles are documented (or if they don't yet exist; in that case, suggest creating docs/principles.md and offer to scaffold a starter file before continuing).
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 · 128 lines · 83 tokens per session scan A ce9b85f9d287
setup is a skill published in the GitHub repository technicalpickles/pickled-claude-plugins (12 stars, last pushed today), licensed MIT. It adds 83 tokens to every session and 1,627 once invoked, about $0.0003 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-09-12.
Other skills, from other repositories
create-pubsub-dotnet
Creates a Dapr pub/sub app in .NET (publisher, subscriber or both) with declarative, programmatic or streaming subscriptions, run with dapr run or Aspire. Use for "create a pub/sub app in .NET" or "build a Dapr publisher and subscriber in C#". For an existing project use add-pubsub-dotnet.
create-agent-dotnet
Creates a durable AI agent app in .NET with Microsoft Agent Framework on Dapr Workflow, run locally with dapr run. Use for "create an agent in .NET" or "scaffold a .NET agent". For Diagrid Catalyst use the catalyst-ai plugin.
create-workflow-from-diagram
Creates a Dapr workflow app from a diagram image (PNG, JPG, GIF, WebP) or a BPMN 2.0 file, in Go, Python, .NET, Java or JavaScript, run locally with dapr run. Use for "create a workflow from this diagram" or "scaffold a workflow from this BPMN". For a Mermaid or hand-drawn sketch, or Diagrid Catalyst, use the…
create-workflow-typescript
Creates a TypeScript Dapr app, run locally with dapr run, that demonstrates Workflow, service invocation, pub/sub, bindings, jobs, state and secrets. Use for "create a workflow in TypeScript" or "create a Dapr app in Node.js". For Diagrid Catalyst use the catalyst-ai plugin.
create-pubsub-python
Creates a Dapr pub/sub app in Python with FastAPI (publisher, subscriber or both) and declarative, programmatic or streaming subscriptions. Use for "create a pub/sub app in Python" or "build a FastAPI publisher and subscriber with Dapr". For an existing app use add-pubsub-python.
create-workflow-dotnet
Creates a Dapr workflow app in .NET, run locally with dapr run. Use for "create a workflow in .NET" or "build a workflow app in C#". For Diagrid Catalyst use the catalyst-ai plugin.