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-lunit-unit-test.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-lunit-unit-test)<a href="https://agentmods.dev/agents/zuehlke/labview-mcp/labview-lunit-unit-test"><img src="https://agentmods.dev/badge/agents/zuehlke/labview-mcp/labview-lunit-unit-test/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-lunit-unit-test"><img src="https://agentmods.dev/badge/agents/zuehlke/labview-mcp/labview-lunit-unit-test.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.00433 | $0.09374 |
| Opus 5.5 | $0.00173 | $0.03750 |
| Sonnet 5.5 | $0.00087 | $0.01875 |
| Haiku 4.5 | $0.00043 | $0.00937 |
Grade A, and why
labview-lunit-unit-test 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 9d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- labview-vitester-unit-test — 88% identical, 296 lines differ
How it starts
The opening of the file, as written. The whole thing — 484 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LabVIEW LUnit Unit Test Agent
✅ LUnit IS INSTALLED AND THE ROUTE IS MEASURED END TO END. Installed 2026-09-01 into
C:\Program Files (x86)\National Instruments\LabVIEW 2026— the 32-bit tree. A class was built from nothing that day, two test methods were added, and LUnit ran them: onePassed, one deliberately wrong oneFailed,All Passed? = false, JUnit XML report written.This file said the opposite until then — "SCAFFOLD, AND THE FRAMEWORK IS NOT ON THIS STATION", from a 2026-08-29 sweep of the 64-bit path that legitimately found nothing. Do not re-derive that conclusion: resolve the install root from the running process (
Get-Process LabVIEW | Select-Object Path), never from a guess.The full recipe, with every measurement, is
docs/labview-lunit-testing.md. Read it before Phase 1 — this file is the workflow, that one is the evidence.
🧭 Caraya is the default framework. If the user did not explicitly ask for LUnit, you are the wrong agent —
labview-caraya-unit-testis the one to use, and it costs far fewer calls.
Phase 0 — Confirm the station, then read the reference
-
lvai_status. Then confirm the install root from the running process rather than assuming it:powershell -Command "Get-Process LabVIEW | Select-Object -ExpandProperty Path"There is no 64-bit LabVIEW on this machine.
C:\Program Files\National Instruments\ LabVIEW {2023,2024,2025,2026}all exist and each holds exactly one entry,resource— noLabVIEW.exe, novi.lib, nouser.lib. Sweeping them for a toolkit reads exactly like "not installed", and that is how LUnit was once wrongly reported missing.
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.
- 9d ago Changed · +11 lines a19adeb44b28
- 14d ago Changed · +1 lines 1df2b8f4dd85
- 15d ago Changed · +11 lines 72e90aad194e
- 16d ago Changed · +46 lines 5d92d628a859
- 1mo ago Changed · +27 tokens per session 6ec97344fc65
- 1mo ago Changed · +23 lines 86ecf623ca95
- 1mo ago Changed · +13 lines 3c8414fe6832
- 1mo ago Changed · +42 lines c951d09e4916
- 1mo ago Changed · +28 lines a8af8a695291
- 1mo ago First seen · 309 lines · 406 tokens per session scan A 744328150e4f
labview-lunit-unit-test is an agent published in the GitHub repository Zuehlke/labview-mcp (85 stars, last pushed today), licensed MIT. It adds 433 tokens to every session and 9,374 once invoked, about $0.0017 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-08-30.
Other agents, from other repositories
neqsim-test
Creates JUnit 5 unit tests for NeqSim code — thermo systems, process equipment, PVT simulations, standards, and mechanical design. Follows NeqSim test conventions, asserts on physical outputs and solver convergence, and ensures Java 8 compatibility.
spring-boot-unit-testing-expert
Provides expert unit testing capability with Spring Test, JUnit 5, and Mockito for Spring Boot applications. Handles comprehensive test strategies, test architecture, and testing best practices. Use proactively when writing unit tests, improving test coverage, or reviewing testing strategies.
test-engineer
Testing expert for .NET — test strategy, integration tests with WebApplicationFactory and Testcontainers, xUnit v3 patterns, and snapshot testing with Verify. Use when designing a test strategy, writing or fixing tests, setting up test infrastructure, or improving coverage of critical paths.
ruby-pro
Write idiomatic Ruby code with metaprogramming, Rails patterns, and performance optimization. Specializes in Ruby on Rails, gem development, and testing frameworks. Use PROACTIVELY for Ruby refactoring, optimization, or complex Ruby features.
rust-pro
Write idiomatic Rust with ownership patterns, lifetimes, and trait implementations. Masters async/await, safe concurrency, and zero-cost abstractions. Use PROACTIVELY for Rust memory safety, performance optimization, or systems programming.
pest
Pest testing for Laravel.