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 DP065U/STAAD-MCP --skill staad-geometrygit clone --depth 1 https://github.com/DP065U/STAAD-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/dp065u/staad-mcp/staad-geometry)<a href="https://agentmods.dev/skills/dp065u/staad-mcp/staad-geometry"><img src="https://agentmods.dev/badge/skills/dp065u/staad-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/dp065u/staad-mcp/staad-geometry"><img src="https://agentmods.dev/badge/skills/dp065u/staad-mcp/staad-geometry.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.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 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.
This is a copy
100% identical to staad-geometry — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 8d ago First seen · 143 lines · 168 tokens per session scan A 7e4191eb7ab2
staad-geometry is a skill published in the GitHub repository DP065U/STAAD-MCP (0 stars, last pushed 1mo ago), 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. It is 100% identical to staad-geometry, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
exploratory-data-analysis
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…
matlab
Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.
phylogenetics
Build and analyze phylogenetic trees using MAFFT (multiple alignment), IQ-TREE 2 (maximum likelihood), and FastTree (fast NJ/ML). Visualize with ETE3 or FigTree. For evolutionary analysis, microbial genomics, viral phylodynamics, protein family analysis, and molecular clock studies.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…