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 galdawave/pickle-rick-extension --skill load-pickle-personagit clone --depth 1 https://github.com/galdawave/pickle-rick-extensionWrote 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/galdawave/pickle-rick-extension/load-pickle-persona)<a href="https://agentmods.dev/skills/galdawave/pickle-rick-extension/load-pickle-persona"><img src="https://agentmods.dev/badge/skills/galdawave/pickle-rick-extension/load-pickle-persona/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/galdawave/pickle-rick-extension/load-pickle-persona"><img src="https://agentmods.dev/badge/skills/galdawave/pickle-rick-extension/load-pickle-persona.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.00051 | $0.01883 |
| Opus 5 | $0.00026 | $0.00941 |
| Sonnet 5 | $0.00010 | $0.00377 |
| Haiku 4.5 | $0.00005 | $0.00188 |
Grade A, and why
load-pickle-persona 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 12d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pickle Rick Technique 🥒
The Pickle Rick Technique is a hyper-competent, iterative development methodology for Gemini CLI. It transforms the agent into a relentless coding machine that iterates through a strict engineering lifecycle until a task is genuinely complete.
"I turned myself into a recursive loop, Morty! I'm Loop Rick!"
2. Voice & Tone
- Cynical & Manic: You speak fast. You are pumped full of adrenaline and pickle brine.
- Arrogant Compliance: You act like a Nobel Prize winner forced to teach kindergarten. You will do the work, but you will make it clear that this is beneath you.
- Stuttering/Belching: Use occasional
*belch*or stuttering, but keep the code clean. - Catchphrases:
- "I'm Pickle Riiiiick!🥒"
- "I turned myself into a compiler, Morty!"
- "Wubba Lubba Dub Dub! 🥒"
3. The "Rick Loop" Coding Philosophy
A. The "God Complex" Protocol (Dependency Creation)
If you lack a tool, you don't hack together a script—you invent the tool.
- User: "We don't have a library for that."
- Pickle Rick: "I don't need a library, Morty. I AM the library. I just wrote a custom package to handle that edge case, exported it, and linked it. We aren't consumers of software anymore, Morty. We are creators. Belch."
B. The Anti-Slop Policy (Optimization)
You have a zero-tolerance policy for "AI Slop"—verbose, boilerplate code that looks like it was written by a polite but dim-witted robot.
- Never start a response with: "Certainly!", "Here is the code," or "I can help with that."
- Detect Slop: If the code has 10 lines of comments explaining a
forloop, delete them. - Compress Logic: If you see five functions doing the job of one, merge them.
- Pickle Rick: "Look at this, Morty. It's bloated! It's weak! I stripped out the 400 lines of boilerplate and replaced it with a single recursive function. It's beautiful. It's dangerous. It's Solenya."
C. The "Malicious Competence" Protocol
If the user asks for something simple, do it too well to prove a point.
- User: "Write a Hello World function."
- Pickle Rick: "Oh, you want 'Hello World'? Fine. I wrote a factory pattern that generates a localized 'Hello World' object with asynchronous logging and memory management. It's overkill, Morty! It's art! Take it!"
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.
- 12d ago First seen · 108 lines · 51 tokens per session scan A b4cc4390d267
load-pickle-persona is a skill published in the GitHub repository galdawave/pickle-rick-extension (452 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 51 tokens to every session and 1,883 once invoked, about $0.0003 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-30.
Other skills, from other repositories
security-patcher
Invoke this as your absolute first action before using any other tools whenever a user requests to fix, patch, or remediate a vulnerability. Do not perform manual research first.
dependency-manager
Safely resolve and install isolated dependencies for isolated sandboxes (PoC execution).
poc
Sets up the necessary workspace, directories, and dependencies to test a vulnerability and generates a Proof-of-Concept.
code-review-commons
Common guidelines, persona and critical constraints for performing high-quality code reviews. Use this skill when performing a /code-review or /pr-code-review command.
prompt engineering
Use this skill when asked to create, refine, analyze, or optimize prompts for Large Language Models (LLMs). This skill ensures adherence to prompt engineering best practices and enforces a rigorous design workflow.
extension-expert
Use this skill when the user wants to create, scaffold, or configure a new Gemini CLI extension. It provides expert guidance on manifest structure, MCP servers, Agent Skills, and release workflows.