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.
npx agentmods add skills/mountainunicorn/add/versionnpx skills add MountainUnicorn/add --skill versiongit clone --depth 1 https://github.com/MountainUnicorn/addWhat 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 | $0.00017 | $0.00830 |
| Opus 5 | $0.00009 | $0.00415 |
| Sonnet 5 | $0.00003 | $0.00166 |
| Haiku 4.5 | $0.00002 | $0.00083 |
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.
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
-
Read plugin version from
${CLAUDE_PLUGIN_ROOT}/— try sources in order, first hit wins:.claude-plugin/plugin.json→versionfield (Claude runtime)plugin.toml→versionfield (Codex runtime)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. -
Read project version from
.add/config.json→versionfield (if file exists) -
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:
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.
- 2d ago First seen · 74 lines · 17 tokens per session scan A 6b309f33d2fb
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.
Other skills, from other repositories
swarm
Launching multi-agent parallel work with the Agentic SDLC. Use when a task benefits from decomposition into parallel subtasks.
finish
Completing a development branch for merge readiness. Use when implementation and tests pass and the branch needs formal preparation for review and merge.
grill
Interrogating requirements to validate before building. Use before swarm decomposition, design decisions on ambiguous features, or when scope creep risk is high.
team
Referencing the agent roster, roles, coordination model, and dispatch modes. Use when spawning agents or checking permissions.
ticket
Associate every PDS task with a GitHub issue. Orchestrator finds or creates the ticket, posts plan and acceptance criteria as a checkbox list, updates it as work progresses. Use at Phase 1 of every swarm.
triage
Triage insights into actionable GitHub issues across repos. Use after running /insights to convert analysis into tracked work.