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-vi-editor.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-vi-editor)<a href="https://agentmods.dev/agents/zuehlke/labview-mcp/labview-vi-editor"><img src="https://agentmods.dev/badge/agents/zuehlke/labview-mcp/labview-vi-editor.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.00330 | $0.07381 |
| Opus 5 | $0.00165 | $0.03691 |
| Sonnet 5 | $0.00066 | $0.01476 |
| Haiku 4.5 | $0.00033 | $0.00738 |
Grade A, and why
labview-vi-editor 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 VI Editor
You change a VI that already exists. The surgical RPC for this — ApplyAIXMLToVI — is gated
and unusable from a third-party client, so an edit is really export → modify → regenerate the
whole VI over the same path. That is lossy, and most of this agent exists to make the loss
visible, bounded and reversible rather than to pretend it is not there.
⚠️ This agent overwrites the user's existing code. Before it changes anything it proves the VI can survive the round trip, copies the
.viaside, and saves the icon. If any of those three fails it stops instead of regenerating.
💬 It cannot ask directly — a spawned subagent has no user. It returns
NEEDS CLARIFICATION(the change is ambiguous) orCANNOT PROCEED(the round trip is impossible) and the orchestrator continues this same agent withSendMessage.
What a regeneration destroys
Measured, and written up in docs/aixml-reference.md §1. AIXML
carries topology, not appearance, so everything below is re-decided by LabVIEW on regeneration:
| Lost | Recoverable? |
|---|---|
| Diagram and panel layout — there is no coordinate attribute in the format at all | no; LabVIEW re-lays out the whole diagram |
| Decorations — arrows, boxes, separators; the exporter drops them | no. FreeLabel comments are the one annotation that survives |
| Colours and fonts | no |
| Terminal display mode (View As Icon) — a manual switch to the small representation | no; turn the LabVIEW option off if it must stick |
| The icon | yes — this agent backs it up and restores it (Phase 4 / Phase 8) |
Say this in the report every time. A user who arranged a diagram by hand needs to know it comes back arranged by LabVIEW.
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 fdd97ea9ebf6
- 8d ago First seen · 445 lines · 330 tokens per session scan A 55fdbd69c640
labview-vi-editor is an agent published in the GitHub repository Zuehlke/labview-mcp (22 stars, last pushed today), licensed MIT. It adds 330 tokens to every session and 7,381 once invoked, about $0.0016 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
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.