version

A version-check command that compares the installed add-on version with the version recorded in a project and reports whether they match.

In plain words
What is it for?
Use it to see the plugin version, project version, and whether the project needs migration after an add-on update.
Why use it?
It makes version drift visible, so an outdated project configuration is less likely to cause confusing behavior or missed updates.

Skill for Claude CodeCodex

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 skills/mountainunicorn/add/version
Any agent
npx skills add MountainUnicorn/add --skill version
Clone the repo
git clone --depth 1 https://github.com/MountainUnicorn/add

Made for: Claude Code, Codex.

Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 830 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.00017 $0.00830
Opus 5 $0.00009 $0.00415
Sonnet 5 $0.00003 $0.00166
Haiku 4.5 $0.00002 $0.00083

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

Security

Grade A, and why

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

core/skills/version/SKILL.md · 74 lines

How it starts

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

ADD Version Command v{{VERSION}}

Show the current ADD version, compare project config version to plugin version, and flag drift.

Execution

  1. Read plugin version from ${CLAUDE_PLUGIN_ROOT}/ — try sources in order, first hit wins:

    1. .claude-plugin/plugin.jsonversion field (Claude runtime)
    2. plugin.tomlversion field (Codex runtime)
    3. VERSION (plain-text, single line — fallback for both runtimes)

    On the Claude runtime, source 1 is authoritative and sources 2–3 are absent. On the Codex runtime (${CLAUDE_PLUGIN_ROOT} resolves to ~/.codex/add), source 1 is absent; read source 2 or 3. Never emit an error if source 1 is missing — fall through quietly.

  2. Read project version from .add/config.jsonversion field (if file exists)

  3. Read core/VERSION if accessible (development installs only)

Output

ADD Version
  Plugin:  v{plugin_version}
  Project: v{project_version}    (from .add/config.json)
  Status:  {status}

Status values:

Condition Status Action
project == plugin ✓ Up to date None
project < plugin ⚠ Project config is behind — migration will run on next skill invocation Suggest: "Run any /add: command to trigger auto-migration, or /add:init --reconfigure for a full refresh."
project > plugin ⚠ Project config is ahead of plugin — you may be on an older plugin version Suggest: "Run: claude plugin update add@add-marketplace"
No .add/config.json ○ Not an ADD project — run /add:init to get started

--check flag

When invoked with --check, output a single machine-readable line and exit:

add:version plugin={plugin_version} project={project_version} status={up_to_date|behind|ahead|uninitialized}

This is for scripting and CI — e.g., a pre-commit hook that warns if the project version is stale.

Changelog summary (when behind)

If project < plugin and a CHANGELOG.md exists at the plugin or repo root, extract the version sections between the project version and the plugin version and display:

Read the full file on GitHub · 74 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 · 74 lines · 17 tokens per session scan A 6b309f33d2fb

Subscribe to this mod's changes

version is a skill published in the GitHub repository MountainUnicorn/add (11 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 830 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.