Borrowing it
Nothing to install: this file belongs to zai-org/Synapse. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/zai-org/Synapse/main/.agents/skills/cc-nano-banana/SKILL.mdgit clone --depth 1 https://github.com/zai-org/SynapseWrote 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/zai-org/synapse/cc-nano-banana)<a href="https://agentmods.dev/skills/zai-org/synapse/cc-nano-banana"><img src="https://agentmods.dev/badge/skills/zai-org/synapse/cc-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/zai-org/synapse/cc-nano-banana"><img src="https://agentmods.dev/badge/skills/zai-org/synapse/cc-nano-banana.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 66 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 66 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00078 | $0.01402 |
| Opus 5.5 | $0.00031 | $0.00561 |
| Sonnet 5.5 | $0.00016 | $0.00280 |
| Haiku 4.5 | $0.00008 | $0.00140 |
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 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- nano-banana — 100% identical, 0 lines differ
- nano-banana — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nano Banana Image Generation
Generate professional images via the Gemini CLI's nanobanana extension.
When to Use This Skill
ALWAYS use this skill when the user:
- Asks for any image, graphic, illustration, or visual
- Wants a thumbnail, featured image, or banner
- Requests icons, diagrams, or patterns
- Asks to edit, modify, or restore a photo
- Uses words like: generate, create, make, draw, design, visualize
Do NOT attempt to generate images through any other method.
Before First Use
- Verify extension is installed:
gemini extensions list | grep nanobanana - If missing, install it:
gemini extensions install https://github.com/gemini-cli-extensions/nanobanana - Verify API key is set:
[ -n "$GEMINI_API_KEY" ] && echo "API key configured" || echo "Missing GEMINI_API_KEY"
Command Selection
| User Request | Command |
|---|---|
| "make me a blog header" | /generate |
| "create an app icon" | /icon |
| "draw a flowchart of..." | /diagram |
| "fix this old photo" | /restore |
| "remove the background" | /edit |
| "create a repeating texture" | /pattern |
| "make a comic strip" | /story |
Available Commands
Note: Always use the --yolo flag to automatically approve all tool actions.
| Command | Use Case |
|---|---|
gemini --yolo "/generate 'prompt'" |
Text-to-image generation |
gemini --yolo "/edit file.png 'instruction'" |
Modify existing image |
gemini --yolo "/restore old_photo.jpg 'fix scratches'" |
Repair damaged photos |
gemini --yolo "/icon 'description'" |
App icons, favicons, UI elements |
gemini --yolo "/diagram 'description'" |
Flowcharts, architecture diagrams |
gemini --yolo "/pattern 'description'" |
Seamless textures and patterns |
gemini --yolo "/story 'description'" |
Sequential/narrative images |
gemini --yolo "/nanobanana prompt" |
Natural language interface |
Common Options
--yolo- Required. Auto-approve all tool actions (no confirmation prompts)--count=N- Generate N variations (1-8)--preview- Auto-open generated images--styles="style1,style2"- Apply artistic styles--format=grid|separate- Output arrangement
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 · 150 lines · 78 tokens per session scan A 8ca02bb1b57e
nano-banana is a skill published in the GitHub repository zai-org/Synapse (488 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 78 tokens to every session and 1,402 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-08-30.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.