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-verify-requirementsgit 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-verify-requirements)<a href="https://agentmods.dev/skills/yxy050208/multisim-mcp/multisim-verify-requirements"><img src="https://agentmods.dev/badge/skills/yxy050208/multisim-mcp/multisim-verify-requirements/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-verify-requirements"><img src="https://agentmods.dev/badge/skills/yxy050208/multisim-mcp/multisim-verify-requirements.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.00045 | $0.00439 |
| Opus 5 | $0.00023 | $0.00219 |
| Sonnet 5 | $0.00009 | $0.00088 |
| Haiku 4.5 | $0.00005 | $0.00044 |
Grade A, and why
multisim-verify-requirements 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 12d 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 设计要求
需要实验 ID 和设计要求。工具名为 Multisim MCP 原始名；Harness 通常添加
mcp__multisim__ 前缀。
- 调用
get_experiment_summary，确认测量列、分析类型和现有验证结果。 - 把每一项要求转换为独立、稳定的 requirement ID、测量 metric、signal、operator、
target 或上下界、容差和单位。不得把定性目标伪装成可测量数值。
周期波形优先使用
frequency；失真要求使用thd，并通过start_x/end_x排除启动过程。噪声边沿应显式设置threshold、hysteresis和min_cycles。 - 调用
verify_experiment_requirements；有理论值时通过theoretical_values提供， 不从模型猜测理论值。 - 对每项列出原要求、判据、实测值、目标、容差、状态和证据。工具返回
unverified时保持该状态，不以最接近值代替通过。 - 若失败源于测量列或分析设置不足，提出最小复测计划；除非用户授权，不自动覆盖 原实验或修改电路。
结论必须同时给出整体状态和 pass/fail/unverified 计数。任何无法从数据证明的安全、 可靠性、热或可制造性声明都不属于仿真通过项。
English summary
Translate each requirement into an explicit measurable criterion, call the verification tool, preserve unverified outcomes, and propose a minimal rerun when the existing analysis cannot supply the required evidence.
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.
- 12d ago First seen · 31 lines · 45 tokens per session scan A acf805e50239
multisim-verify-requirements is a skill published in the GitHub repository yxy050208/multisim-mcp (10 stars, last pushed 2d ago), licensed MIT. It adds 45 tokens to every session and 439 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
red-team-review
Unified adversarial review: v4.3 Strategic Matrix (MTA-004). 7-phase framework: Priors → Rubric → Adversarial Lenses → SWOT/TOWS → MCDA Decision Engine → Blind Spot/Kill Switch → Executive Summary. Absorbs: bias-detector.
code-review
Perform a structured code review of changes, checking for correctness, style, tests, and potential issues.
cli-command
Design, implement, or review Composio CLI commands under ts/packages/cli using Effect, effect/unstable/cli, services, output conventions, configuration and environment variables, and local vendor references. Use for CLI command UX, command wiring, service changes, or CLI source edits. Do not use for CLI E2E-only work…
deploy
Use when ready to ship — runs pre-push gates (lint, typecheck, build, tests, security sweep), commits, releases, and pushes. Standalone, never auto-invoked. Push always requires explicit confirmation. Trigger with /hyperflow:deploy, "ship it", "ready to push", "release", "cut a release", "deploy".
trace
Use when encountering bugs, test failures, runtime errors, broken builds, or "this doesn't work" reports. Systematic root-cause analysis before any patch — never blind-patches symptoms. Standalone, ends with a final-integration review of the fix. Trigger with /hyperflow:trace, "debug this", "find the root cause", "why…
review
Structured PR review for pygraphistry. Input: PR number/branch (default current branch PR). Output: findings and convergence artifacts under plans/ /. Method: multi-wave, evidence-first review across spec, correctness, tests, security, code quality, DRY, concurrency, performance, architecture, operability, and…