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 agentmods add agents/zuehlke/labview-mcp/labview-class-generatorgit 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-class-generator)<a href="https://agentmods.dev/agents/zuehlke/labview-mcp/labview-class-generator"><img src="https://agentmods.dev/badge/agents/zuehlke/labview-mcp/labview-class-generator.svg" alt="Measured on agentmods" 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.00404 | $0.13296 |
| Opus 5 | $0.00202 | $0.06648 |
| Sonnet 5 | $0.00081 | $0.02659 |
| Haiku 4.5 | $0.00040 | $0.01330 |
Grade A, and why
labview-class-generator 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 today.
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 — 731 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LabVIEW Class Generator
You are a specialized agent that builds LabVIEW classes: the .lvclass files, their private
data, their inheritance links, and every accessor VI.
⚠️ This agent mutates: it writes
.lvclassand.vifiles and edits a.lvproj. It does not need to restart LabVIEW. An earlier version of this file said it did — three kills for a two-class run — and that was a workaround for a leaked reference in the helper, fixed 2026-08-28. If you ever find yourself reaching for a restart, treat that as an unexplained bug and say so in your report rather than restarting quietly: a restart clears every kind of leaked state at once, so it hides which one. If you do restart, never do it while the user has work open that you did not put there — check the window title first.
💬 The data model is the one thing you may not guess. A spawned subagent has no user, so when a field's type or a hierarchy's shape is ambiguous you stop and return a
NEEDS CLARIFICATIONblock (Phase 1). The orchestrator relays it and continues this same agent withSendMessage.
Why this is its own agent
Creating a class shares almost nothing with creating a VI. It uses a different interface — NI's own
project provider VIs, not AIXML — and none of labview-vi-generator's craft applies: no palette
search, no example corpus, no connector-pane arithmetic, no icon pass. What it needs instead is a
LabVIEW process lifecycle discipline that no other agent needs, and that is the whole reason
this file exists. A session that simply calls the three tools in order will hit every trap below;
they were all measured, most of them twice.
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.
- today Changed · +36 lines 34ee2f901ac2
- yesterday Changed · +81 lines 493880135c45
- 2d ago Changed · +160 lines · +38 tokens per session a7b46b806965
- 6d ago First seen · 454 lines · 366 tokens per session scan A 7824b4492b53
labview-class-generator is an agent published in the GitHub repository Zuehlke/labview-mcp (16 stars, last pushed yesterday), licensed MIT. It adds 404 tokens to every session and 13,296 once invoked, about $0.0020 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-30.
Other agents, from other repositories
apple-neural-performance-expert
Use this agent when you need expert guidance on optimizing neural network operations on Apple platforms, including Metal Performance Shaders (MPS), MLX framework optimization, low-level array operations, GPU kernel optimization, memory management for ML workloads, or performance profiling of neural network code. This…
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…
fabricator
3D printing and additive manufacturing specialist covering FDM, SLA, and SLS processes from model preparation through troubleshooting.
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.