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 yxy050208/multisim-mcp --skill multisim-debug-circuitgit clone --depth 1 https://github.com/yxy050208/multisim-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/yxy050208/multisim-mcp/multisim-debug-circuit)<a href="https://agentmods.dev/skills/yxy050208/multisim-mcp/multisim-debug-circuit"><img src="https://agentmods.dev/badge/skills/yxy050208/multisim-mcp/multisim-debug-circuit/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/yxy050208/multisim-mcp/multisim-debug-circuit"><img src="https://agentmods.dev/badge/skills/yxy050208/multisim-mcp/multisim-debug-circuit.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.00049 | $0.00536 |
| Opus 5 | $0.00024 | $0.00268 |
| Sonnet 5 | $0.00010 | $0.00107 |
| Haiku 4.5 | $0.00005 | $0.00054 |
Grade A, and why
multisim-debug-circuit 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.
What it actually says
调试 Multisim 电路
本 skill 引用 Multisim MCP 原始工具名；Harness 默认前缀为 mcp__multisim__。
- 保存问题描述、原始网表、分析命令、错误日志和已有实验 ID，不覆盖原始设计。
- 调用
runtime_status，把安装/COM/模板故障与电路故障分开。 - 对结构化设计先调用
diagnose_design；若已有同一设计的完成实验目录，把它作为experiment_dir附加。按顺序复核：网表语法、地节点、悬空节点、短路、极性、单位、 偏置、模型、分析命令、采样范围、饱和以及收敛条件。 - 若只有实验 ID，先用
get_experiment_summary，再按需读取log、netlist、commands或report；不要把二进制文件送入模型上下文。 - 提出能够解释故障的最小修改，明确修改前值、修改后值、理由和回滚方法。
- 把该最小修改写成明确
DesignPatch，调用evaluate_design_patch在同一硬性验收规范 下复测原设计和内存候选。若设计带权威source_netlist，只有确认需要时才显式允许 候选内存网表再生。不要把adoption_eligible当作提交授权。 - 检查前后诊断、两次实验和递归 manifest；失败或证据不足时保留“失败/未验证”。
- 只有用户另行批准时，才把通过候选交给本机审批绑定的持久化流程。
输出采用“症状—证据—根因—最小修改—复测结果—剩余风险”结构。不要在没有 复测数据时宣称问题已经解决。
English summary
Separate environment failures from circuit defects, inspect bounded evidence, apply the smallest reversible change, rerun into a new output directory, and compare measured results before declaring the issue fixed.
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 Changed · +4 lines 465b3f13c6ad
- 9d ago First seen · 28 lines · 49 tokens per session scan A 876d5b20c33b
multisim-debug-circuit is a skill published in the GitHub repository yxy050208/multisim-mcp (9 stars, last pushed 6d ago), licensed MIT. It adds 49 tokens to every session and 536 once invoked, about $0.0002 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
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.
ios-simulator
Verify and debug native, React Native, Expo, or Flutter apps on an iOS Simulator with agent-device. Use when an agent needs to launch an app, inspect its live UI, tap, type, scroll, validate a code change, collect failure evidence, or reproduce a workflow on an iPhone or iPad Simulator.
debugging-executions
Debug failed or wrong-output workflow executions using executions tools. Load when the user reports execution failures, unexpected node output, empty parameter values after a successful run, or a node showing a red or failed expression error.
atmos-schemas
JSON Schema for Atmos: stack-manifest and atmos.yaml config schemas, IDE auto-completion, validate stacks/schema/config, SchemaStore integration.
issue
Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the…
therapeutic-ifs
Unified inner work engine: Schema deconstruction (diagnosis) + IFS therapy (treatment). Absorbs: schema-deconstruction.