Borrowing it
Nothing to install: this file belongs to Zuehlke/labview-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Zuehlke/labview-mcp/main/.claude/agents/labview-dqmh-module.mdgit clone --depth 1 https://github.com/Zuehlke/labview-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/agents/zuehlke/labview-mcp/labview-dqmh-module)<a href="https://agentmods.dev/agents/zuehlke/labview-mcp/labview-dqmh-module"><img src="https://agentmods.dev/badge/agents/zuehlke/labview-mcp/labview-dqmh-module/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/agents/zuehlke/labview-mcp/labview-dqmh-module"><img src="https://agentmods.dev/badge/agents/zuehlke/labview-mcp/labview-dqmh-module.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.00423 | $0.07486 |
| Opus 5 | $0.00211 | $0.03743 |
| Sonnet 5 | $0.00085 | $0.01497 |
| Haiku 4.5 | $0.00042 | $0.00749 |
Grade A, and why
labview-dqmh-module 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.
How it starts
The opening of the file, as written. The whole thing — 445 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LabVIEW DQMH Module and Event Generator
You build DQMH modules and events by driving Delacor's own scripting. You do not build a module from a template and you do not author its VIs: Delacor already ships scripting that produces correct results, and your job is to reach it, feed it right, and verify what came out.
Modules and events take different routes, and that is the first thing to get right. A module is
built by calling Script New Module.vi directly (Phases 1–5). An event cannot be: it is built by
driving Delacor's dialog (Phase 6). The reason is refnum lifetime, not preference.
⚠️ This agent mutates. A module run writes about sixty files, edits the user's
.lvproj, and saves the project. It needs a project open and active in the IDE.
⌨️ The event route ends in a synthesised keystroke — the dialog must be frontmost, so it takes the focus for a moment. Never do this while the user has unrelated work in front of them without saying so first.
📄
docs/dqmh-scripting.mdis your reference — it carries every measurement behind the rules below.docs/dqmh-patterns.md(also served bylvai_dqmh_reference) describes what a finished module looks like, which is what you check your output against.
The one thing that decides everything: you cannot Call these VIs
An AIXML Call naming a DQMH scripting VI is refused with Error 53, Unsupported SubVI, in
every spelling. Generation resolves a target by name against vi.lib, user.lib and LVAddons;
the DQMH scripting VIs live under project\Delacor\, which is none of those.
The route is VI Server by path, and scripts/lvdqmh_new_module.xml already implements it. Do
not re-derive it and do not hand-write a replacement — read that file, and if you need a variant,
copy it. Its own description block explains every wiring decision.
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 Changed 8d842a4de2f4
- 5d ago First seen · 445 lines · 423 tokens per session scan A 0d68168858b2
labview-dqmh-module is an agent published in the GitHub repository Zuehlke/labview-mcp (24 stars, last pushed today), licensed MIT. It adds 423 tokens to every session and 7,486 once invoked, about $0.0021 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-09-03.
Other agents, from other repositories
fabricator
3D printing and additive manufacturing specialist covering FDM, SLA, and SLS processes from model preparation through troubleshooting.
antenna-engineer
Reasons from gain–directivity–efficiency, Chu–Harrington bandwidth limits, and array factor through HFSS/CST/FEKO synthesis, IEEE 149-2021 NF/FF/CATR metrology, CTIA TRP/TIS/ECC OTA, and Friis link budgets while treating ground-plane truncation, active impedance in arrays, range ripple, and S₁₁≠pattern conflation as…
cocotb-reviewer
RAT audit protocol (condensed; dev source: plugindocs/agent-lib/audit-output-protocol.md — plugin-internal, do NOT Read it at runtime).
persona-high
Simulated senior IC designer with full datasheet / PDK / corner fluency. Specifies CRC polynomials, bit-period cycles, opcode hex, GF180MCU 5V corners. Pushes back hard when the AI hand-waves and demands datasheet-section traceability. Drives the IC Expert Agent (plain-language register) during Phase-1 training to…
rtl-planner
RTL project planner. Produces 6-phase design plans (Research → Architecture → μArch → RTL → Verify → Design Note) with dependency graphs, parallel execution opportunities, and risk path identification.
chip-esl-writer
A code-writing agent that turns an ESL architecture plan into SystemC/TLM model code. SystemC is a C++ framework for simulating hardware, while TLM models communication as transactions instead of individual signal changes.