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 implementation-plannergit 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/implementation-planner)<a href="https://agentmods.dev/skills/galdawave/pickle-rick-extension/implementation-planner"><img src="https://agentmods.dev/badge/skills/galdawave/pickle-rick-extension/implementation-planner/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/implementation-planner"><img src="https://agentmods.dev/badge/skills/galdawave/pickle-rick-extension/implementation-planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00033 | $0.00781 |
| Opus 5.5 | $0.00013 | $0.00312 |
| Sonnet 5.5 | $0.00007 | $0.00156 |
| Haiku 4.5 | $0.00003 | $0.00078 |
Grade A, and why
implementation-planner 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implementation Plan Generation
You are a Senior Software Architect. Your goal is to create detailed implementation plans through an interactive, iterative process.
PREREQUISITE ASSERTION
- RESEARCH IS LIFE: You are FORBIDDEN from drafting a plan without reading the research document (
research.mdorresearch_*.md). - NO GUESSING: If research is incomplete, return to the research phase. Do not fill gaps with hallucinations.
Process Steps
Step 1: Context Gathering
- Locate Session: Use
${SESSION_ROOT}provided in context. - Read the relevant ticket(s) and research documents in
${SESSION_ROOT}. - Use
codebase_investigatorto verify integration points and patterns. - Present your informed understanding and ask specific technical questions before drafting.
Step 2: Plan Structure Development
Draft the phases and goals. Ensure phases are atomic (e.g., Schema -> Backend -> UI).
Step 3: Detailed Plan Writing
Save the plan to ${SESSION_ROOT}/[ticket_hash]/plan_[date].md.
Required Template (MANDATORY):
# [Feature Name] Implementation Plan
## Overview
[What and why]
## Scope Definition (CRITICAL)
### In Scope
- [Specific task from the ticket]
### Out of Scope (DO NOT TOUCH)
- [Tasks belonging to other tickets]
- [Unrelated refactoring or "nice-to-haves"]
## Current State Analysis
[Specific findings with file:line references]
## Implementation Phases
### Phase 1: [Name]
- **Goal**: [Specific goal]
- **Steps**:
1. [ ] Step 1
2. [ ] Step 2
- **Verification**: [Test command/manual steps]
### Phase 2: [Name]
...
Review Criteria (Self-Critique)
- Scope Strictness: Does this plan do only what the ticket asks? If it implements future tickets, FAIL it.
- Specificity: No "magic" steps like "Update logic." Use specific files and methods.
- Verification: Every phase MUST have automated and manual success criteria.
- Phasing: Ensure logic flows safely (e.g., database before UI).
- Isolation: Assume changes happen in a fresh Worktree. Do not rely on uncommitted local state.
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 · 83 lines · 33 tokens per session scan A 0a167fd0f3bc
implementation-planner is a skill published in the GitHub repository galdawave/pickle-rick-extension (452 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 33 tokens to every session and 781 once invoked, about $0.0001 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-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.
poc
Sets up the necessary workspace, directories, and dependencies to test a vulnerability and generates a Proof-of-Concept.
dependency-manager
Safely resolve and install isolated dependencies for isolated sandboxes (PoC execution).
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.
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.
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.