Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/UI5/plugins-coding-agentsnpx agentmods add skills/ui5/plugins-coding-agents/modernize-test-starterWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/ui5/plugins-coding-agents/modernize-test-starter)<a href="https://agentmods.dev/skills/ui5/plugins-coding-agents/modernize-test-starter"><img src="https://agentmods.dev/badge/skills/ui5/plugins-coding-agents/modernize-test-starter/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/ui5/plugins-coding-agents/modernize-test-starter"><img src="https://agentmods.dev/badge/skills/ui5/plugins-coding-agents/modernize-test-starter.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 316 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00244 | $0.04844 |
| Opus 5.5 | $0.00098 | $0.01938 |
| Sonnet 5.5 | $0.00049 | $0.00969 |
| Haiku 4.5 | $0.00024 | $0.00484 |
Grade A, and why
modernize-test-starter 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 1mo 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 — 374 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Modernize to Test Starter
This skill modernizes a UI5 project's entire test infrastructure — both unit tests and OPA5 integration tests — to the Test Starter concept.
Reference: Blog post: Simplify Your Test Setup
Why Modernize
The Test Starter replaces per-test HTML bootstrapping with a single generic test page and a declarative testsuite.qunit.js configuration. Benefits: eliminates boilerplate HTML/JS, handles QUnit/Sinon/coverage setup automatically, ensures CSP compliance, provides consistent configuration, enables per-test isolation and parallel execution.
NEVER Skip Test Starter Modernization
OPA5 test HTML files are ALWAYS convertible — they follow a mechanical pattern. Invalid excuses: "complex mock server" (lives in host, not entry point), "sap.ui.define monkey-patching" (same), "FLP sandbox bootstrap" (same), "too many files" (batch-process), "too complex" (invalid).
| Type | Example | Action |
|---|---|---|
| Test Driver | opa/<Area>/<TestName>.qunit.html |
CONVERT to Test Starter |
| Test Host | test<ServiceName>.html |
KEEP AS-IS (app-under-test in iframe) |
| Test Suite | testsuite.qunit.html |
REPLACE with testsuite.qunit.js |
| Dev Sandbox | flpSandbox.html |
IGNORE |
The only real technical challenge: OPA5 entry points may use jQuery.sap.require() for QUnit bootstrap libs — replace with sap.ui.require or note that Test Starter loads them automatically.
Pre-requisites
Read manifest.json → sap.app/id. This is your namespace:
<NAMESPACE>— dots → slashes (e.g.,my.app→my/app)<NAMESPACE-WITH-DOTS>— raw value with dots
Phase 0: Detection
0.1 Check for unit tests
Look for webapp/test/unit/ containing unitTests.qunit.html, unitTests.qunit.js, allTests.js, AllTests.js, or allTests.qunit.js. Identify all legacy aggregator files — JS files whose only purpose is loading other test modules via sap.ui.require/sap.ui.define with no actual test logic (QUnit.module, QUnit.test, assert.*). Their contents will be inlined into unitTests.qunit.js and the files deleted.
What ships with it
11 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.
- references/linter-invisible-patterns.md 791 B
- references/pattern-a-modernization.md 6.8 KB
- references/pattern-b-modernization.md 9.2 KB
- references/pattern-u-iframe-migration.md 28 KB
- references/testsuite-configuration.md 8.2 KB
- scripts/check-dangling-entries.js 9.5 KB runs code
- scripts/check-dangling-entries.test.js 7.1 KB runs code
- scripts/detect-cross-window-imports.js 11 KB runs code
- scripts/detect-cross-window-imports.test.js 8.6 KB runs code
- scripts/parse-testsuite.js 25 KB runs code
- scripts/parse-testsuite.test.js 14 KB runs code
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.
- 1mo ago First seen · 374 lines · 244 tokens per session scan A ab286f304a88
modernize-test-starter is a skill published in the GitHub repository UI5/plugins-coding-agents (40 stars, last pushed yesterday), licensed Apache-2.0. It adds 244 tokens to every session and 4,844 once invoked, about $0.0010 per session on Opus 5.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
pn-testing-strategy
Testing strategy and pyramid. Unit/integration/E2E ratio, Vitest vs Playwright vs MSW, contract testing, and test-environment setup. Use when defining or reviewing a project's testing approach.
webapp-testing
Write and run comprehensive web app tests — unit, integration, E2E with Playwright/Cypress, and visual regression.
testing-patterns
Vitest + Playwright testing patterns: unit tests, mocking, fixtures, E2E, coverage, and anti-patterns. Use when writing tests, setting up test infrastructure, or following TDD workflows.
javascript-testing-patterns
Comprehensive guide for implementing robust testing strategies in JavaScript/TypeScript applications using modern testing frameworks and best practices.
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
axiom-testing
Use when writing ANY test, debugging flaky tests, making tests faster, or choosing Swift Testing vs XCTest. Covers unit tests, UI tests, async testing, test architecture.