nano_banana_2 is Nano Banana Pro, not Nano Banana 2

The piece is less a model shootout than a billing and authentication audit. Because Claude Code cannot draw pixels, every image or video skill is a wrapper that routes to a provider, and the wrapper determines which account is charged. The survey surfaces how tangled that routing gets: Nano Banana Pro alone is reachable via OpenRouter, Pilio, Higgsfield's youtube-thumbnail skill, and fal.ai through the ECC video-editing skill, each with its own invoice.

It also documents structural inconsistencies that can quietly cost money. Higgsfield's general skill defaults to quality and tells the agent not to optimize for cheaper models unless asked, so a vague request bills the premium default. The deer-flow skills switch providers based on which environment variable happens to be set, and the guide notes a GEMINI_API_KEY set for another purpose can pull billing toward Gemini unless the provider is pinned explicitly.

Finally, the install guidance differs by author: Higgsfield's skills bootstrap with a curl-piped install script, while RunComfy's ai-video-generation explicitly forbids piping remote scripts into a shell. The practical takeaway is that provider choice, key placement, and install method should be settled before an agent touches any of these skills.