ty-physical-model-debugging

ty-physical-model-debugging is a skill for Claude Code, Codex from Suzhou-Tongyuan/sysplorer-mcp-server. It costs 79 tokens per session (2,013 once invoked), scanned A, original, MIT.

A troubleshooting workflow for existing Sysplorer Modelica physical models, which describe physical systems with equations and components. It investigates failed translations, simulations, initialization, events, numerical problems, and external C code.

In plain words
What is it for?
Use it to diagnose or repair problems involving generated solvers, state selection, index reduction, nonlinear equations, runtime numbers, initialization, events, and external C functions.
Why use it?
It helps separate the cause of a model failure from its symptoms and avoids changing a model without evidence. It can either report the diagnosis or make a verified repair when authorized.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to diagnose or repair problems involving generated solvers, state selection, index reduction, nonlinear equations, runtime numbers, initialization, events, and external C functions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/suzhou-tongyuan/sysplorer-mcp-server/ty-physical-model-debugging
Install

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.

Any agent
npx skills add Suzhou-Tongyuan/sysplorer-mcp-server --skill ty-physical-model-debugging
Clone the repo
git clone --depth 1 https://github.com/Suzhou-Tongyuan/sysplorer-mcp-server

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for ty-physical-model-debugging

README.md
[![agentmods](https://agentmods.dev/badge/skills/suzhou-tongyuan/sysplorer-mcp-server/ty-physical-model-debugging/github.svg)](https://agentmods.dev/skills/suzhou-tongyuan/sysplorer-mcp-server/ty-physical-model-debugging)
Your own site
<a href="https://agentmods.dev/skills/suzhou-tongyuan/sysplorer-mcp-server/ty-physical-model-debugging"><img src="https://agentmods.dev/badge/skills/suzhou-tongyuan/sysplorer-mcp-server/ty-physical-model-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.

agentmods 80×15 button for ty-physical-model-debugging

Your own site · 80×15
<a href="https://agentmods.dev/skills/suzhou-tongyuan/sysplorer-mcp-server/ty-physical-model-debugging"><img src="https://agentmods.dev/badge/skills/suzhou-tongyuan/sysplorer-mcp-server/ty-physical-model-debugging.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 79 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,013 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00079 $0.02013
Opus 5.5 $0.00032 $0.00805
Sonnet 5.5 $0.00016 $0.00403
Haiku 4.5 $0.00008 $0.00201

Measured 19d ago against content hash 117dd428fbf3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ty-physical-model-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.

The scan reads SKILL.md. This mod also ships 3 executable files (scripts/debug_workspace.py, scripts/extract_debug_evidence.py, scripts/query_sysplorer_help.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

resources/modeling_skills/ty-physical-model-debugging/SKILL.md · 184 lines

How it starts

The opening of the file, as written. The whole thing — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Physical Model Debugging

Use evidence to diagnose, or repair one verified task-owned copy. Record source and working identities separately; preserve package/resource references, public C signatures and experiment settings. Before physical-model edits or delivery, load applicable ty-sysplorer-modeling-rules constraints, including Gate 6 for changed graphical targets. Pure log diagnosis does not load its full workflow.

Task Mode and Applicable Constraints

Enter directly from a concrete fault; neither the modeling router nor the debug router is a prerequisite. Select diagnose_only or repair from the request. In diagnose-only mode, inspect and, only if authorized, reproduce the needed stage; report the cause or evidence gap and stop without a patch. Offline review does not authorize execution. Repairs follow the workflow below.

Record the requested terminal stage and user acceptance before execution. Reuse the existing attributable baseline, valid session, and task-owned working copy; do not reroute, replan, or recreate them when loading another skill's constraints. Construction-stage debugging returns to the original construction task.

Fast Path

For a simple single-file or single-package fault, keep the workflow near 12 external calls when practical.

  1. Read the staged source and SHA-256 once. Do not scan Git, unrelated directories, helper source, or large generated artifacts.
  2. Extract every functional acceptance invariant supplied by the user, including values, signs, units, ranges, stop time, and KPIs.
  3. Confirm the target through Sysplorer MCP before first live access: use session_manager(action="probe") when available, then health. Reuse valid same-session evidence; recheck after a switch, disconnection or infrastructure symptom. Offline artifact inspection needs no session call. Resolve unknown API contracts before calling; do not enumerate all APIs.
  4. Reproduce once through the first failed stage: check -> translate -> initialize/simulate. Stop at the first failure.
  5. Form one falsifiable hypothesis, make one minimal reversible patch in the work copy, and read back the exact change.
  6. Rerun the affected stage and the requested terminal chain after its cheaper prerequisites pass. Static-only acceptance does not require simulation.
  7. Verify original hashes and temporary-settings restoration. Verify end time for required runtime acceptance and KPIs only when requested or necessary to resolve the reported abnormal result; otherwise mark them not_required.

Read the full file on GitHub · 184 lines

Changes

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.

  1. 19d ago First seen · 184 lines · 79 tokens per session scan A 117dd428fbf3

Subscribe to this mod's changes

ty-physical-model-debugging is a skill published in the GitHub repository Suzhou-Tongyuan/sysplorer-mcp-server (10 stars, last pushed 20d ago), licensed MIT. It adds 79 tokens to every session and 2,013 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.

Related

Other skills, from other repositories

trace

Evidence-driven tracing lane that orchestrates competing tracer hypotheses in Claude built-in team mode.

Yeachan-Heo/oh-my-claudecode · 18 tokens

pos-tagging-fixes

Diagnose and fix part-of-speech tagging in the compromise source repository. Choose between lexical data, ambiguity clues, indexed neighbour rules, preTagger logic, and postTagger patterns with attention to execution order, side effects, runtime, and bundle size. Use for internal tagging changes, not ordinary…

spencermountain/compromise · 72 tokens

smiles-validation

Strict SMILES validation, structural comparison, and modification verification. Catches invalid LLM-generated molecules.

synthetic-sciences/openscience · 24 tokens

linear-solvers

Select and configure linear solvers for systems Ax=b in dense and sparse problems. Use when choosing direct vs iterative methods, diagnosing convergence issues, estimating conditioning, selecting preconditioners, or debugging stagnation in GMRES/CG/BiCGSTAB.

beita6969/ScienceClaw · 55 tokens

nonlinear-solvers

Select and configure nonlinear solvers for f(x)=0 or min F(x). Use for Newton methods, quasi-Newton (BFGS, L-BFGS), Broyden, Anderson acceleration, diagnosing convergence issues, choosing line search vs trust region, and analyzing Jacobian quality.

beita6969/ScienceClaw · 63 tokens

numerical-stability

Analyze and enforce numerical stability for time-dependent PDE simulations. Use when selecting time steps, choosing explicit/implicit schemes, diagnosing numerical blow-up, checking CFL/Fourier criteria, von Neumann analysis, matrix conditioning, or detecting stiffness in advection/diffusion/reaction problems.

beita6969/ScienceClaw · 61 tokens