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/tinusj/swing-mcp/swing-ui-testingnpx skills add TinusJ/swing-mcp --skill swing-ui-testinggit clone --depth 1 https://github.com/TinusJ/swing-mcpWrote 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/tinusj/swing-mcp/swing-ui-testing)<a href="https://agentmods.dev/skills/tinusj/swing-mcp/swing-ui-testing"><img src="https://agentmods.dev/badge/skills/tinusj/swing-mcp/swing-ui-testing.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00051 | $0.01194 |
| Opus 5 | $0.00026 | $0.00597 |
| Sonnet 5 | $0.00010 | $0.00239 |
| Haiku 4.5 | $0.00005 | $0.00119 |
Grade A, and why
swing-ui-testing 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 5d 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.
Core Concepts
Deterministic synchronisation: Never rely on sleeps. Use wait_for with an explicit condition (COMPONENT_TEXT, COMPONENT_VISIBLE, COMPONENT_ENABLED, COMPONENT_EXISTS, COMPONENT_GONE, WINDOW_TITLE, WINDOW_COUNT, EDT_IDLE) and a timeoutMs to make test steps deterministic.
Fresh snapshots: Component UIDs come from take_snapshot and can go stale after any action that changes the UI. Re-snapshot before asserting on state, and whenever an interaction fails to find a component.
Assert via the model, not pixels: Prefer get_component_details, get_table_data, and get_list_items for assertions — they read the actual Swing model state. Use take_screenshot only for visual verification.
Workflow Patterns
1. Test session setup and teardown
launch_appwith the application's full java command (useattach_to_apponly when the app must keep running after the test).wait_forwithWINDOW_TITLE(orWINDOW_COUNT) to ensure the main window is up before interacting.- Run the scenario steps.
stop_appto end the session, even on failure, so the launched JVM is cleaned up.
2. Form filling and validation
take_snapshot(optionallyfilter: "ENABLED_ONLY") to find input fields and buttons.filleach text field, spinner, or editable combo box; usetype_textwhen the form relies on key listeners or per-keystroke validation.select_optionfor combo boxes andclickfor checkboxes/radio buttons.- Submit with
clickon the confirm button, orpress_keywithENTER. - Verify:
wait_fora success condition, then check resulting state withget_component_details(e.g. an error label's text, or a button becoming enabled/disabled).
3. Tables, lists, and trees
- Verify data:
get_table_datawithstartRow/endRowto assert column names and cell values;get_list_itemsforJListitems or visibleJTreerows. - Select:
select_table_cell(row/col),select_option(index or visible text),select_tree_nodewith aRoot > Folder > Leafpath. - Row actions: after selecting, use
clickwithclickType: "DOUBLE"to open, orselect_context_menu_itemfor the row's context menu. - Long content:
scrollinside theJScrollPaneto reach off-screen rows before interacting via mouse emulation.
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.
- 5d ago First seen · 74 lines · 51 tokens per session scan A 1bedc72f1c2b
swing-ui-testing is a skill published in the GitHub repository TinusJ/swing-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 1,194 once invoked, about $0.0003 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-31.
Other skills, from other repositories
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
run-integration-tests
Build, pack, and run .NET MAUI integration tests locally. Validates templates, samples, and end-to-end scenarios using the local workload.
cli-e2e-testcase-writer
Use when adding or updating Go CLI E2E coverage for one tests/clie2e/{domain} domain of the compiled lark-cli, especially when the work requires live --help or schema exploration, scenario-based clie2e.RunCmd workflows, and per-domain coverage.md maintenance.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
__SKILL_ID__
This fixture verifies that skill content can be written into the target sandbox and queried back immediately.
harness-test-writer
Add regression test cases to the Bifrost provider harness (the Postman collection run via make run-provider-harness-test) based on a merged PR or a GitHub issue. Fetches the PR/issue, traces the affected wire path in the codebase, checks existing harness coverage, designs cases following harness conventions, inserts…