Borrowing it
Nothing to install: this file belongs to JanGoebel/LabVIEW-MCP-Server-Toolkit. 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/JanGoebel/LabVIEW-MCP-Server-Toolkit/main/CLAUDE.mdgit clone --depth 1 https://github.com/JanGoebel/LabVIEW-MCP-Server-ToolkitWrote 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/instructions/jangoebel/labview-mcp-server-toolkit/claude-md)<a href="https://agentmods.dev/instructions/jangoebel/labview-mcp-server-toolkit/claude-md"><img src="https://agentmods.dev/badge/instructions/jangoebel/labview-mcp-server-toolkit/claude-md/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/instructions/jangoebel/labview-mcp-server-toolkit/claude-md"><img src="https://agentmods.dev/badge/instructions/jangoebel/labview-mcp-server-toolkit/claude-md.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.02409 | $0.02409 |
| Opus 5.5 | $0.00964 | $0.00964 |
| Sonnet 5.5 | $0.00482 | $0.00482 |
| Haiku 4.5 | $0.00241 | $0.00241 |
Grade A, and why
LabVIEW-MCP-Server-Toolkit CLAUDE.md scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
requests (`tools/test/Test-McpServer.ps1` where present, otherwise curl). How it starts
The opening of the file, as written. The whole thing — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working on the LabVIEW MCP Server Toolkit with Claude Code
Instructions for Claude Code sessions in this repository. They describe how work is done here: who decides what, how LabVIEW code is changed, and how commits and pull requests are structured.
The project
A LabVIEW toolkit that turns VIs into an MCP server over HTTP (tools, prompts, resources). Built on the IG HTTP Server Toolkit and JSONtext.
| Path | Content |
|---|---|
src/MCP Server/ |
The toolkit: MCP Server.lvlib and the MCP Handler.lvclass HTTP handler |
src/*.vipb, src/*.vipc |
Package build specification and runtime dependencies |
tests/ |
Caraya tests (MCP Server tests.lvlib); Run_Tests_CLI.vi is the CI entry point |
examples/ |
Example servers. In this repo they load the toolkit from src, not from an installed package |
tools/ci/ |
Pull request review scripts and the workflow template |
tools/setup/, tools/test/ |
Environment setup and the protocol tester, where present |
tools/icons/ |
New-VIIcon.ps1, which draws VI icons in the toolkit's style |
docs/ |
Guides for working on the repository, e.g. pull-request-reports.md |
.github/workflows/ |
CI. Maintainer-only, see below |
Who decides what
- The maintainer reviews and merges every pull request. Never merge, and never
push to
main. - Releases are the maintainer's: never create or push tags, never create releases, never trigger the release workflow.
- Files under
.github/workflows/are changed by the maintainer only. The token used here cannot push them. Put workflow changes intools/ci/as a template and describe the exact edit in the pull request. - GitHub settings (rulesets, variables, runners, environments) are the maintainer's. Say what is needed; do not try to change them.
- Never ask for tokens, passwords or serial numbers in chat. Sign-ins happen in the maintainer's own terminal.
Branches
- Always work on a branch created from
origin/mainaftergit fetch. Name it after the change (http-transport-behaviour,fix-package-build). - One topic per branch and pull request. Unrelated work gets its own branch, even when it comes up in the same session.
- If work depends on an open pull request, branch from that pull request's branch and say so in the description.
- VIs are binary and cannot be merged. Do not open two pull requests that edit the same VI; if two tasks need the same VI, say so and ask which goes first.
- Follow-up changes to an open pull request are new commits on its branch, announced with a short update comment (see "Pull requests"). The pull request updates itself; do not open a new one.
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 · +6 lines · +126 tokens per session d3a5f47aea22
- 12d ago Changed · +9 lines · +128 tokens per session 02657f9b0643
- 15d ago First seen · 166 lines · 2,155 tokens per session scan A 186dbaee45ca
LabVIEW-MCP-Server-Toolkit CLAUDE.md is an instructions file published in the GitHub repository JanGoebel/LabVIEW-MCP-Server-Toolkit (65 stars, last pushed 4d ago), licensed MIT. It adds 2,409 tokens to every session, about $0.0096 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-15.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.