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 Suzhou-Tongyuan/sysplorer-mcp-server --skill ty-sysplorer-debugginggit clone --depth 1 https://github.com/Suzhou-Tongyuan/sysplorer-mcp-serverWrote 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/suzhou-tongyuan/sysplorer-mcp-server/ty-sysplorer-debugging)<a href="https://agentmods.dev/skills/suzhou-tongyuan/sysplorer-mcp-server/ty-sysplorer-debugging"><img src="https://agentmods.dev/badge/skills/suzhou-tongyuan/sysplorer-mcp-server/ty-sysplorer-debugging/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/suzhou-tongyuan/sysplorer-mcp-server/ty-sysplorer-debugging"><img src="https://agentmods.dev/badge/skills/suzhou-tongyuan/sysplorer-mcp-server/ty-sysplorer-debugging.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.00080 | $0.01189 |
| Opus 5.5 | $0.00032 | $0.00476 |
| Sonnet 5.5 | $0.00016 | $0.00238 |
| Haiku 4.5 | $0.00008 | $0.00119 |
Grade A, and why
ty-sysplorer-debugging 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 19d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sysplorer Debugging Router
This is an independent entrypoint, not a mandatory child of the modeling skill. Known domains can enter either specialist directly without this router. Identify the fault domain and coordinate specialists; do not repeat their repair loops.
Task Mode and Handoff
- Identify
diagnose_onlyorrepairfrom the user's request. A request only to explain or locate a fault does not authorize edits. Reproduce only when the request authorizes execution; explicit offline review uses supplied artifacts. - Record the requested terminal stage and acceptance conditions. Reuse available model identity, session evidence, first attributable diagnostic, baseline, settings and work-copy/checkpoint. Unknown fields stay unknown; do not query unrelated data merely to fill a report.
- Use the smallest evidence needed to choose a specialist. Hand off the existing context once. Do not recreate the workspace, replan, or reproduce a baseline already attributable to the current model/settings.
- Summarize the specialist's evidence and scope-qualified status. For mixed faults, coordinate another layer only when current evidence requires it.
Routing
| Evidence | Route |
|---|---|
| Modelica equations, initialization, runtime, external function, or build produced by Modelica translation | ty-physical-model-debugging |
| Confirmed Sysblock restriction, ports/blocks, CCaller, or build produced by Sysblock code generation | ty-sysblock-model-debugging |
| Generated solver without a known origin | Identify restriction and generating pipeline before choosing a specialist |
| Mixed model | Follow the implicated layer; reuse valid child evidence and verify interfaces when the fault crosses the boundary |
Do not preload both specialists or all references. A known top-level fault does
not require rerunning every child. Ordinary diagram work uses
ty-sysblock-diagram-modeling; domain construction uses its existing modeling
skill. Construction-stage failures retain the original task owner and working
model, invoke scoped debugging, then resume construction.
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/current-mcp-recipes.md 6.9 KB
- references/external-c-debugging.md 5.8 KB
- references/help-doc-index.md 3.1 KB
- references/report-contract.md 2.5 KB
- scripts/debug_workspace.py 14 KB runs code
- scripts/extract_debug_evidence.py 11 KB runs code
- scripts/query_sysplorer_help.py 11 KB runs code
- skill_info.json 753 B
- SKILL_ZH.md 4.3 KB
- 使用说明.md 1.5 KB
- 版本说明.md 1.2 KB
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.
- 19d ago First seen · 99 lines · 80 tokens per session scan A 2d4584d3712d
ty-sysplorer-debugging is a skill published in the GitHub repository Suzhou-Tongyuan/sysplorer-mcp-server (10 stars, last pushed 20d ago), licensed MIT. It adds 80 tokens to every session and 1,189 once invoked, about $0.0003 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-10-13.
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…
ci-fixer
CI failures - read error, minimal fix, verify.
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.
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…