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 BentleySystems/openstaad-mcp --skill staad-geometrygit clone --depth 1 https://github.com/BentleySystems/openstaad-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/skills/bentleysystems/openstaad-mcp/staad-geometry)<a href="https://agentmods.dev/skills/bentleysystems/openstaad-mcp/staad-geometry"><img src="https://agentmods.dev/badge/skills/bentleysystems/openstaad-mcp/staad-geometry/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/skills/bentleysystems/openstaad-mcp/staad-geometry"><img src="https://agentmods.dev/badge/skills/bentleysystems/openstaad-mcp/staad-geometry.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00168 | $0.02229 |
| Opus 5 | $0.00084 | $0.01115 |
| Sonnet 5 | $0.00034 | $0.00446 |
| Haiku 4.5 | $0.00017 | $0.00223 |
Grade A, and why
staad-geometry 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:
- staad-geometry — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
STAAD.Pro Geometry Modeling
Instructions
- Define the shorthand once per script:
geo = staad.Geometry
Creating Elements
geo.AddNode(x, y, z)→ node ID (coordinates in base unit)geo.AddBeam(startNode, endNode)→ beam IDgeo.AddPlate(n1, n2, n3, n4)→ plate ID — pass 4 separate int args, NOT a list- Triangle: the API always takes 4 args; pass
0as a sentinel for the missing 4th node →geo.AddPlate(n1, n2, n3, 0)
- Triangle: the API always takes 4 args; pass
geo.AddSolid(n1, n2, n3, n4, n5, n6, n7, n8)→ solid ID
Bulk Creation (more efficient than loops)
geo.AddMultipleNodes([[x,y,z], ...])→ list of node IDsgeo.AddMultipleBeams([[start,end], ...])→ list of beam IDsgeo.AddMultiplePlates([[n1,n2,n3,n4], ...])→ list of plate IDs- Triangle rows: each row must have exactly 4 ints; use
0as the sentinel 4th element →[n1, n2, n3, 0]
- Triangle rows: each row must have exactly 4 ints; use
Explicit ID Creation
geo.CreateNode(nodeNo, x, y, z)— creates node with a specific IDgeo.CreateBeam(beamNo, startNode, endNode)— beam with specific IDgeo.CreatePlate(plateNo, nA, nB, nC, nD)— plate with specific ID- Triangle: pass
0fornD(the sentinel for a missing 4th node) →geo.CreatePlate(id, nA, nB, nC, 0)
- Triangle: pass
geo.CreateSolid(solidNo, nA, nB, nC, nD, nE, nF, nG, nH)— solid with specific ID
Shared Element ID Sequence
IMPORTANT: Beams, plates, and solids share a SINGLE continuous ID counter.
- If you create 10 beams (IDs 1–10) then 4 plates, plates get IDs 11–14, NOT 1–4
- NEVER assume element IDs start at 1 for each type
- Always retrieve actual IDs:
geo.GetBeamList(),geo.GetPlateList(),geo.GetSolidList()
Quick Reference
| Function | Returns | Notes |
|---|---|---|
GetNodeCount() |
int |
total nodes |
GetMemberCount() |
int |
total beams |
GetPlateCount() |
int |
total plates |
GetSolidCount() |
int |
total solids |
GetNodeList() |
list |
all node IDs |
GetBeamList() |
list |
all beam IDs |
GetPlateList() |
list |
all plate IDs |
GetSolidList() |
list |
all solid IDs |
GetLastNodeNo() |
int |
highest node ID |
GetLastBeamNo() |
int |
highest beam ID |
GetNodeCoordinates(nid) |
(x,y,z) |
|
GetMemberIncidence(bid) |
(start,end) |
start/end node IDs |
GetPlateIncidence(pid) |
(n1,n2,n3,n4) |
0 if triangle |
GetBeamLength(bid) |
float |
in base units |
GetNodeDistance(nA, nB) |
float |
distance between two nodes |
IsColumn(bid, tol) |
bool |
True if near-vertical (tol in degrees) |
IsBeam(bid, tol) |
bool |
True if near-horizontal |
IsOrphanNode(nid) |
bool |
True if not connected |
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 First seen · 143 lines · 168 tokens per session scan A 7e4191eb7ab2
staad-geometry is a skill published in the GitHub repository BentleySystems/openstaad-mcp (42 stars, last pushed yesterday), licensed MIT. It adds 168 tokens to every session and 2,229 once invoked, about $0.0008 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 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.