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 xi-zhao/OpenQuantum --skill mqt-debuggergit clone --depth 1 https://github.com/xi-zhao/OpenQuantumWrote 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/xi-zhao/openquantum/mqt-debugger)<a href="https://agentmods.dev/skills/xi-zhao/openquantum/mqt-debugger"><img src="https://agentmods.dev/badge/skills/xi-zhao/openquantum/mqt-debugger/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/xi-zhao/openquantum/mqt-debugger"><img src="https://agentmods.dev/badge/skills/xi-zhao/openquantum/mqt-debugger.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.00051 | $0.00540 |
| Opus 5.5 | $0.00020 | $0.00216 |
| Sonnet 5.5 | $0.00010 | $0.00108 |
| Haiku 4.5 | $0.00005 | $0.00054 |
Grade A, and why
mqt-debugger 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 3d 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
MQT Debugger
原生 SDK 路径
本能力使用 MQT Debugger 的原生公开 API。用户需要 OpenQASM 程序、单步仿真、断言、影响范围与错误诊断 时，由 Agent 在固定依赖环境中编写和运行任务代码。
使用 node scripts/sdk-access.mjs inspect mqt-debugger 定位环境，按完整 SDK 工作流执行。模块导航：mqt.debugger；导航不是 API 白名单。
状态/纠缠/等式断言与候选错误原因分别解释，诊断提示不是唯一根因证明。DAP 或真实 QPU 检查需要相应入口和授权。
本入口复用宿主文件与代码工具，没有新增通用执行 Tool。原生 SDK 受上游版本、可选依赖、宿主资源与用户授权约束。已禁用或被拒绝的动作不能借代码路径绕过。执行状态和科研验收分别报告。
状态/纠缠/等式断言与候选错误原因分别解释，诊断提示不是唯一根因证明。DAP 或真实 QPU 检查需要相应入口和授权。
按固定版本的公开文档和签名选择方法；输入、算法与资源预算由任务决定。该 Skill 通过原生 SDK 工作台和宿主代码工具执行自定义程序，没有新增通用执行服务或专用计算 Tool。
保留程序、输入、完整结果、依赖锁摘要和实际检查。原生 API 的执行不推导最终科学验收，scientificValidation=not_evaluated。
原生程序示例
固定版本的可编辑程序展示公开 API 的使用方式，参数与模型可按研究任务修改。先显式准备环境，再在独立任务目录运行，保留结果文件；示例检查不构成最终科学验收。
What ships with it
3 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.
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.
- 3d ago First seen · 32 lines · 51 tokens per session scan A 47eebd2f6a32
mqt-debugger is a skill published in the GitHub repository xi-zhao/OpenQuantum (75 stars, last pushed yesterday), licensed MIT. It adds 51 tokens to every session and 540 once invoked, about $0.0002 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-14.
Other skills, from other repositories
opik-explain
Root-cause a specific Opik trace, or a pattern across traces, and return a grounded explanation. Uses the hosted Opik MCP when it is connected, and falls back to SDK scripting otherwise. Returns the root cause, the evidence spans as clickable Opik UI links, and one suggested next step. Use for "why did this trace…
ask-good-questions
Guidance for asking technical questions and reporting bugs so another developer can reproduce and answer them. It covers versions, environment details, minimal reproduction steps, expected and actual results, errors, and attempted fixes.
perf-optimize
A performance-improvement guide that requires measuring real behaviour before changing code. It explains how to identify bottlenecks, test one change at a time, and check that the change did not break anything.
blazemeter-troubleshooting
Comprehensive troubleshooting guide for BlazeMeter, covering API Monitoring, Performance Testing, general issues, integrations, and security. Use when troubleshooting for (1) API Monitoring issues (Radar Agent auth, SSL certificates, debug tests), (2) Performance Testing issues (high response time, 500 errors, partial…
trace-form
Trace how an Oracle Forms screen actually works — which form opens a modal, where a button's code really lives when its body looks empty, what a :GLOBAL carries back into a field. Use when asked how a Forms form, block, item, button, modal window or LOV behaves, where a value comes from, what calls what, or when a…
feedback-nudge
Use when the user wants to report a bug, request a feature, or send feedback to the Zooza engineering team. Also offer proactively after a successful commit operation (max once per week).