upgrade

A command that updates the nano-banana-image-editor plugin from its marketplace repository. A plugin is an add-on that extends the coding agent.

In plain words
What is it for?
Use it to verify the installed version and repository, fetch the latest tags, and guide an upgrade.
Why use it?
It checks the current installation and looks for a newer version so the image editor can be updated.

Command

Install

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.

agentmods
npx agentmods add commands/emdashcodes/claude-code-plugins/upgrade
Clone the repo
git clone --depth 1 https://github.com/emdashcodes/claude-code-plugins
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,572 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00016 $0.01572
Opus 5 $0.00008 $0.00786
Sonnet 5 $0.00003 $0.00314
Haiku 4.5 $0.00002 $0.00157

Measured 2d ago against content hash 1fc3f9de9015, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

upgrade 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 2d 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.

plugins/nano-banana-image-editor/commands/upgrade.md · 232 lines

How it starts

The opening of the file, as written. The whole thing — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Nano Banana Image Editor Plugin Upgrade

You are running the nano-banana-image-editor upgrade command to update the plugin to the latest version.

Your Task

Guide the user through upgrading the nano-banana-image-editor plugin by pulling the latest changes from the marketplace repository.

Workflow

Step 1: Verify Current Installation

Check the current version and installation location:

# Get marketplace directory
MARKETPLACE_DIR=$(dirname $(dirname ${CLAUDE_PLUGIN_ROOT}))

# Get current version from marketplace.json
CURRENT_VERSION=$(jq -r '.plugins[] | select(.name=="nano-banana-image-editor") | .version' "$MARKETPLACE_DIR/.claude-plugin/marketplace.json")

# Verify git repository
cd "$MARKETPLACE_DIR" && git rev-parse --git-dir >/dev/null 2>&1 && echo "✓ Git repository found" || echo "✗ Not a git repository"

Output to user:

Current version: [version]
Marketplace directory: [path]

Step 2: Check for Updates

Fetch the latest tags and check for updates:

cd "$MARKETPLACE_DIR"
git fetch --tags origin

Then get the version information:

# Get the latest version tag for this plugin
LATEST_TAG=$(git tag -l 'nano-banana-image-editor/v*' --sort=-v:refname | head -n 1)

# Get current tag (if on a tag)
CURRENT_TAG=$(git describe --tags --exact-match 2>/dev/null || echo "none")

# Filter to only nano-banana-image-editor tags if we're on a tag
if [ "$CURRENT_TAG" != "none" ]; then
  echo "$CURRENT_TAG" | grep -q '^nano-banana-image-editor/' || CURRENT_TAG="none"
fi

echo "Latest tag: $LATEST_TAG"
echo "Current tag: $CURRENT_TAG"

Analyze the output:

  • If LATEST_TAG is empty → No tagged releases available yet
  • If CURRENT_TAG equals LATEST_TAG → Already on latest version
  • If LATEST_TAG is newer → Continue to Step 3
  • If git fetch fails → Inform user there's a connection issue

Output to user:

Current version: [CURRENT_VERSION] (tag: [CURRENT_TAG or "not on a tagged release"])
Latest available: [LATEST_TAG]

Read the full file on GitHub · 232 lines

Changes

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.

  1. 2d ago First seen · 232 lines · 16 tokens per session scan A 1fc3f9de9015

Subscribe to this mod's changes

upgrade is a command published in the GitHub repository emdashcodes/claude-code-plugins (13 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 1,572 once invoked, about $0.0001 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.