update

An update command for checking and installing new KARIMO versions published as GitHub releases.

In plain words
What is it for?
Use it to check for updates, install the latest release after confirmation, force an update, or run the check without installing.
Why use it?
It avoids manually checking the project version, downloading updates, and handling configuration changes.

Command for Claude Code

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/opensesh/karimo/update
Clone the repo
git clone --depth 1 https://github.com/opensesh/KARIMO

Made for: Claude Code.

Per session 0 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,454 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.00000 $0.01454
Opus 5 $0.00000 $0.00727
Sonnet 5 $0.00000 $0.00291
Haiku 4.5 $0.00000 $0.00145

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

Security

Grade A, and why

update 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

  • update — 100% identical, 0 lines differ
.claude/plugins/karimo/commands/update.md · 203 lines

How it starts

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

/karimo:update — Update Command

Check for and apply KARIMO updates from GitHub releases.

Usage

/karimo:update              # Check for updates and install if available
/karimo:update --check      # Only check for updates, don't install
/karimo:update --force      # Update even if already on latest version

Behavior

Step 1: Run Update Script

Execute the update script:

bash .karimo/update.sh

For check-only mode:

bash .karimo/update.sh --check

For force update:

bash .karimo/update.sh --force

Step 2: Interpret Results

The script will:

  1. Check current version from .karimo/VERSION
  2. Fetch latest release from GitHub (opensesh/KARIMO)
  3. Compare versions using semver
  4. Show what will be updated (if update available)
  5. Apply updates after user confirmation

Step 3: Check Config Version & Run Migrations

After update script completes successfully, check if config migration is needed:

# Get current config version
if [ -f .karimo/config.yaml ]; then
    config_version=$(grep -E "^config_version:" .karimo/config.yaml | sed 's/.*"\(.*\)".*/\1/' || echo "unknown")
else
    echo "Warning: No config.yaml found, skipping migrations"
    config_version="unknown"
fi

# Get latest KARIMO version (should match updated VERSION file)
karimo_version=$(cat .karimo/VERSION)

echo "Config version: $config_version"
echo "KARIMO version: $karimo_version"

# Determine if migration needed
if [ "$config_version" != "unknown" ] && [ "$config_version" != "$karimo_version" ]; then
    echo
    echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
    echo "Config Migration Required"
    echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
    echo "Your config: v$config_version"
    echo "Latest KARIMO: v$karimo_version"
    echo

    # Check for migration scripts
    migration_count=0
    for script in .karimo/migrations/v*.sh; do
        if [ -f "$script" ] && [ -x "$script" ]; then
            # Extract version numbers from script name (e.g., v1-to-v2.sh)
            script_name=$(basename "$script")
            if [[ "$script_name" =~ v([0-9.]+)-to-v([0-9.]+) ]]; then
                from_ver="${BASH_REMATCH[1]}"
                to_ver="${BASH_REMATCH[2]}"

                # Check if this migration applies to current config
                if [ "$config_version" = "$from_ver" ]; then
                    echo "Running migration: $script_name"
                    echo "  From: v$from_ver"
                    echo "  To:   v$to_ver"
                    echo

                    # Run migration
                    if bash "$script" .karimo/config.yaml; then
                        echo "✓ Migration succeeded: v$from_ver → v$to_ver"
                        echo
                        config_version="$to_ver"  # Update for next migration
                        migration_count=$((migration_count + 1))
                    else
                        echo "✗ Migration failed: $script_name"
                        echo
                        echo "Error: Config migration failed. Please review the error above."
                        echo "Your config has been backed up to: .karimo/config.yaml.backup-*"
                        echo
                        exit 1
                    fi
                fi
            fi
        fi
    done

    if [ $migration_count -eq 0 ]; then
        echo "No migrations found for v$config_version → v$karimo_version"
        echo
        echo "Manual migration may be required. See:"
        echo "  .karimo/migrations/README.md"
        echo
    else
        echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
        echo "✓ Applied $migration_count migration(s)"
        echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
        echo
    fi
elif [ "$config_version" = "$karimo_version" ]; then
    echo "Config is up to date (v$config_version)"
fi

Read the full file on GitHub · 203 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 · 203 lines · 0 tokens per session scan A 4f4d07ca4139

Subscribe to this mod's changes

update is a command published in the GitHub repository opensesh/KARIMO (283 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,454 tokens. 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.