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 ruizrica/agent-pi --skill nano-bananagit clone --depth 1 https://github.com/ruizrica/agent-piWrote 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/ruizrica/agent-pi/nano-banana)<a href="https://agentmods.dev/skills/ruizrica/agent-pi/nano-banana"><img src="https://agentmods.dev/badge/skills/ruizrica/agent-pi/nano-banana/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/ruizrica/agent-pi/nano-banana"><img src="https://agentmods.dev/badge/skills/ruizrica/agent-pi/nano-banana.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.00061 | $0.00491 |
| Opus 5 | $0.00030 | $0.00246 |
| Sonnet 5 | $0.00012 | $0.00098 |
| Haiku 4.5 | $0.00006 | $0.00049 |
Grade A, and why
nano-banana 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 13d 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.
What it actually says
Nano Banana Image Generation
Use this skill when the user wants an image back, either from a fresh prompt or from editing an existing image.
Model
- Provider: OpenRouter
- Model:
google/gemini-3.1-flash-image-preview - Friendly name: Nano Banana
Supported workflows
- Text-to-image: user provides a prompt, you generate an image.
- Image edit: user provides an image or screenshot plus instructions, you generate a modified image.
Before you run
- Make sure the prompt is explicit enough to produce the desired image.
- If editing an image, first save or locate the input image path in the workspace.
- The script writes generated files to
.context/generated-images/by default.
Usage
Generate a new image
node agent/skills/nano-banana/generate-image.js \
--prompt "A clean product hero shot of a matte black coffee grinder on a soft beige background, studio lighting" \
--output .context/generated-images/coffee-grinder.png
Edit an existing image
node agent/skills/nano-banana/generate-image.js \
--prompt "Keep the layout the same, but change the CTA button to green, replace the headline with 'Ship faster', and make the page look more premium" \
--input-image path/to/screenshot.png \
--output .context/generated-images/edited-screenshot.png
Response handling
- The script prints JSON with an
outputfield containing the saved image path. - After running it, tell the user the output file path.
- If the model returns no image, inspect the JSON warning and summarize the failure clearly.
Notes
- Prefer PNG outputs unless the user asks for another format.
- Preserve existing composition when the user asks for modifications to a screenshot.
- If the user’s request is ambiguous, clarify what should change and what must remain untouched.
What ships with it
3 files beside SKILL.md 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.
- 13d ago First seen · 58 lines · 61 tokens per session scan A 2b8478694fcc
nano-banana is a skill published in the GitHub repository ruizrica/agent-pi (269 stars, last pushed 1mo ago), licensed MIT. It adds 61 tokens to every session and 491 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…