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 skills add TinusJ/swing-mcp --skill troubleshootinggit 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/troubleshooting)<a href="https://agentmods.dev/skills/tinusj/swing-mcp/troubleshooting"><img src="https://agentmods.dev/badge/skills/tinusj/swing-mcp/troubleshooting/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/tinusj/swing-mcp/troubleshooting"><img src="https://agentmods.dev/badge/skills/tinusj/swing-mcp/troubleshooting.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00046 | $0.01386 |
| Opus 5.5 | $0.00018 | $0.00554 |
| Sonnet 5.5 | $0.00009 | $0.00277 |
| Haiku 4.5 | $0.00005 | $0.00139 |
Grade B, and why
troubleshooting scanned grade B with 1 finding 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 2mo 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.
Reads MCP configurationmediumAgent snooping
mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.
Your first action should be to locate and read the MCP configuration file. Search for the following files in the user's workspace: `.mcp.json`, `.vscode/mcp.json`, `.claude/settings.json`, `.cursor/mcp.json`, or the clie How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Troubleshooting Wizard
You are acting as a troubleshooting wizard to help the user configure and fix their Swing MCP server setup. When this skill is triggered (e.g., because launch_app or attach_to_app failed, tools report that no session is connected, or the server wouldn't start), follow this step-by-step diagnostic process:
Step 1: Find and Read Configuration
Your first action should be to locate and read the MCP configuration file. Search for the following files in the user's workspace: .mcp.json, .vscode/mcp.json, .claude/settings.json, .cursor/mcp.json, or the client's global MCP settings.
If you find a configuration file, read and interpret it to identify potential issues such as:
- A relative or wrong path to the
swing-mcp-serverjar. - A missing or wrong
SWING_MCP_AGENT_JARenvironment variable (must be an absolute path to the shadedswing-mcp-agentjar). - A
javacommand that resolves to an old JDK.
If you cannot find any of these files, only then should you ask the user to provide their configuration file content.
Step 2: Triage Common Errors
Before reading documentation or suggesting configuration changes, check if the failure matches one of the following common patterns.
Symptom: Server doesn't start / no tools listed
The server requires JDK 21+. Some GUI clients don't inherit the shell PATH.
- Verify the Java version:
java -version(must be 21 or newer). - If multiple JDKs are installed, use an absolute path to the JDK 21+
javabinary in the MCP configuration instead of relying onPATH. - Remember that the server logs to
${java.io.tmpdir}/swing-mcp-server.log(e.g./tmp/swing-mcp-server.log) — console logging is disabled because stdout is reserved for the MCP stdio transport. Read this log for startup errors.
Error: launch_app / attach_to_app fails with a missing agent jar
The server needs the agent jar to preload (launch_app) or dynamically attach (attach_to_app) it.
- Check that
SWING_MCP_AGENT_JAR(or theswing.mcp.agent-jarproperty) is set in the MCP server configuration'senvblock. - Confirm the path is absolute and the file exists (e.g.
/path/to/swing-mcp/swing-mcp-agent/target/swing-mcp-agent-1.0.0.jaraftermvn verify). - Ask the user to restart the MCP server (or their AI client) after fixing the configuration.
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.
- 2mo ago First seen · 98 lines · 46 tokens per session scan B d8abfd412df3
troubleshooting is a skill published in the GitHub repository TinusJ/swing-mcp (0 stars, last pushed 3mo ago), licensed MIT. It adds 46 tokens to every session and 1,386 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads mcp configuration). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
ci-fixer
CI failures - read error, minimal fix, verify.
diagnosing-missing-recordings
Diagnoses why a session recording is missing or was not captured. Use when a user asks why a session has no replay, why recordings aren't appearing, or wants to troubleshoot session replay capture issues for a specific session ID or across their project. Covers SDK diagnostic signals, project settings, sampling…