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 skills add node-opcua/node-opcua-modeler-mcp-server --skill node-opcua-modeler-mcp-servergit clone --depth 1 https://github.com/node-opcua/node-opcua-modeler-mcp-serverWrote 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/skills/node-opcua/node-opcua-modeler-mcp-server/node-opcua-modeler-mcp-server)<a href="https://agentmods.dev/skills/node-opcua/node-opcua-modeler-mcp-server/node-opcua-modeler-mcp-server"><img src="https://agentmods.dev/badge/skills/node-opcua/node-opcua-modeler-mcp-server/node-opcua-modeler-mcp-server.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.00070 | $0.00763 |
| Opus 5 | $0.00035 | $0.00381 |
| Sonnet 5 | $0.00014 | $0.00153 |
| Haiku 4.5 | $0.00007 | $0.00076 |
Grade A, and why
opcua-modeling 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 8d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OPC UA Modeling with the OPC UA Modeler MCP Server
When to use this skill
Use it whenever a task involves OPC UA information modeling:
- designing a NodeSet2 / information model for a machine or device
- choosing which companion specification types to derive from
- checking what components, properties, methods, or optionals a type has
- validating namespace dependencies (
di,machinery,robotics, …) - finding the correct UNECE engineering-unit symbol (
°C,l/min,N·m)
Never invent OPC UA type names, browse paths, or unit symbols from memory — companion specs are too niche for that. Query the catalog instead: the answers come from the official published NodeSet2.xml files.
Workflow
list_namespaces— see the ~28 available companion specs with aliases, URIs, and dependency lists. Pick the spec(s) matching the domain (e.g.scalesfor weighing,ladsfor lab devices).search_types/list_types— find candidate types by keyword (e.g. "weighing") or enumerate everything a spec defines.get_type_details— get a type's full structure: components, properties, methods, interfaces,subtypeOfchain, andavailableOptionals— the exhaustive list of valid optional browse paths (including nested dotted paths likedi:Identification.machinery:InitialOperationDate).resolve_dependencies— given the spec aliases you use, get the complete transitively-resolved, load-ordered namespace list to declare.find_engineering_unit— map natural language ("litre per minute") to the valid UNECE symbol before writing any EUInformation.
Rules of thumb
- Anchor on companion-spec base types. Subclass the closest existing
type (e.g.
scales:ScaleDeviceType, notua:BaseObjectType) so clients recognize the model. optionals:entries MUST come fromavailableOptionals. Never guess optional paths and never re-declare inherited components — inherited members come for free from the supertype.- Declare only the namespaces you use, in the dependency order returned
by
resolve_dependencies. - Types missing from a spec are a signal to compose (add components) rather than to invent look-alike type names.
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.
- 8d ago First seen · 66 lines · 70 tokens per session scan A cf718becdb9e
opcua-modeling is a skill published in the GitHub repository node-opcua/node-opcua-modeler-mcp-server (1 stars, last pushed 11d ago), licensed Apache-2.0. It adds 70 tokens to every session and 763 once invoked, about $0.0003 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-31.
Other skills, from other repositories
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
jetson-diagnostic
Read-only Jetson health snapshot for identity, memory, GPU, thermal, power, storage, services, and top processes.
doca-socket-relay
Use this skill when the operator is driving the DOCA Socket Relay to bridge a socket-oriented host application onto a BlueField DPU peer without rewriting it — picking the deployment shape (in-process, sidecar, or BlueField service container), configuring the host-side socket and the DPU-side forwarding endpoint…
offensive-z-wave
Z-Wave attack methodology — sniffing with Z-Force / EZ-Wave / RTL-SDR + ZniffMobile, S0 (legacy) network-key derivation flaw and key reuse, S2 (modern) ECDH commissioning analysis, replay/injection on unauthenticated nodes, default-key brute-force on test deployments, and home-automation hub pivots. Use when targeting…
hsb-flash
Flash the FPGA on an HSB board connected to an NVIDIA devkit. Supports HSB Lattice boards (FPGA versions 2407, 2412, 2507, 2510) and Leopard Imaging VB1940 "all-in-one" cameras (FPGA versions 2507, 2510). Uses release-specific YAML manifests and board-type-specific program commands. Lattice and VB1940 commands must…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.