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/ui5/webcomponents-react/ui5wc-upgradenpx skills add UI5/webcomponents-react --skill ui5wc-upgradegit clone --depth 1 https://github.com/UI5/webcomponents-reactWhat 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.00079 | $0.03051 |
| Opus 5 | $0.00039 | $0.01525 |
| Sonnet 5 | $0.00016 | $0.00610 |
| Haiku 4.5 | $0.00008 | $0.00305 |
Grade A, and why
ui5wc-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.
How it starts
The opening of the file, as written. The whole thing — 393 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI5 Web Components Upgrade Protocol
Follow each step in order. Do NOT skip verification gates.
Prerequisites
Ensure the working tree is clean before starting (git status should show no uncommitted changes). The upgrade touches many files across multiple packages, and a dirty tree makes it hard to isolate upgrade-related changes and risks committing unrelated work.
Initialization
- Parse the target version from the argument (e.g.
2.25.0or2.25.1). - Derive the tilde range
~TARGET_VERSIONfor peerDependencies (e.g.~2.25.1). - Read the current version from root
package.json→dependencies["@ui5/webcomponents"]. - If current matches target, ask if the user wants to re-run wrapper generation only (skip to Step 2).
- Check if Renovate already updated root deps — if
dependencies["@ui5/webcomponents"]already matches target, note that Step 1a can be skipped.
Step 1: Update Dependencies
1a. Root package.json
Skip if Renovate already handled this.
Update to the exact target version:
dependencies: @ui5/webcomponents, @ui5/webcomponents-fiori, @ui5/webcomponents-ai, @ui5/webcomponents-compat, @ui5/webcomponents-icons
devDependencies: @ui5/webcomponents-tools
@ui5/webcomponents-baseis NOT a direct root dependency — only update it in peerDependencies.
1b. Package peerDependencies
Update tilde ranges to ~TARGET_VERSION in all sub-packages. See references/package-json-peer-deps.md for the exact map. Summary:
| File | Keys to update |
|---|---|
packages/main/package.json |
@ui5/webcomponents, -base, -fiori, -icons |
packages/base/package.json |
@ui5/webcomponents-base |
packages/ai/package.json |
@ui5/webcomponents-ai |
packages/compat/package.json |
@ui5/webcomponents-compat, @ui5/webcomponents-react |
packages/cypress-commands/package.json |
@ui5/webcomponents, -base |
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 393 lines · 79 tokens per session scan A 1fcd71f22474
ui5wc-upgrade is a skill published in the GitHub repository UI5/webcomponents-react (539 stars, last pushed 2d ago), licensed Apache-2.0. It adds 79 tokens to every session and 3,051 once invoked, about $0.0004 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
metrics-instrumentation
Specification for instrumenting an opik-backend workflow with operational OpenTelemetry metrics — per-stage throughput/latency/error counters and native histograms, dimensioned per-customer (workspace). Use when a pipeline (scoring, ingestion, experiments, jobs) needs per-stage visibility. Covers metric emission only…
obsidian-markdown
Explain, draft, or validate Obsidian Flavored Markdown syntax: properties, wikilinks, embeds, callouts, tags, comments, highlights, block references, math, and Mermaid. Use when the user explicitly requests Obsidian note formatting or syntax help, not for general Markdown or broad vault operations.
wiki-lint
Run a deterministic, read-only health check on an Obsidian wiki. Use for lint, vault health check, audit wiki health, find orphans, find dead links, frontmatter audit, provenance audit, or wiki audit. Reports graph, link, frontmatter, provenance-ledger, empty-section, and stale-index findings; it does not reason…
new-changelog
Create the next desktop changelog entry when asked to add a changelog file or prepare the next release note under packages/changelog/content. Use this when the task is specifically about determining the next version and creating the markdown entry.
git-safety
Git safety rules. INVOKE WHEN: git push, force push, git reset, git clean, destructive git, push force, reset hard. NEVER force push or do destructive git operations.
predictor-hand-skill
Expert knowledge for AI forecasting — superforecasting principles, signal taxonomy, confidence calibration, reasoning chains, and accuracy tracking.