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-steel-designgit 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-steel-design)<a href="https://agentmods.dev/skills/dp065u/staad-mcp/staad-steel-design"><img src="https://agentmods.dev/badge/skills/dp065u/staad-mcp/staad-steel-design/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-steel-design"><img src="https://agentmods.dev/badge/skills/dp065u/staad-mcp/staad-steel-design.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.00173 | $0.01307 |
| Opus 5 | $0.00086 | $0.00654 |
| Sonnet 5 | $0.00035 | $0.00261 |
| Haiku 4.5 | $0.00017 | $0.00131 |
Grade A, and why
staad-steel-design 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 11d 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-steel-design — 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
STAAD.Pro Steel Design
Instructions
Design Workflow — 5 Steps
Step 1 — Create design brief
brief_ref = design.CreateDesignBrief(1067) # AISC 360-16
| Code | Standard |
|---|---|
| 1067 | AISC 360-16 |
| 1061 | AISC 360-10 |
| 1045 | AISC 360-05 |
| 1004 | BS 5950-1:2000 |
| 1220 | BS EN 1993-1-1 (Eurocode 3) |
| 1032 | IS 800 2007 LSD |
| 1149 | AS 4100 |
| 1182 | CSA S16-14 |
Step 2 — Assign design commands to members
design.AssignDesignCommand(brief_ref, 'CHECK CODE', '', beam_list)
# Returns True on success and raises on failure (execute_code reports any error)
| Command | Description |
|---|---|
| CHECK CODE | Verify member capacity against the code |
| SELECT | Optimize section (pick the lightest passing section) |
| TAKE OFF | Generate material take-off report |
Step 3 — Save to persist design commands
staad.SaveModel(True)
Step 4 — Run analysis + design
staad.SetSilentMode(True)
status = staad.AnalyzeEx(1, 0, 1) # silentMode=1, hiddenMode=0, waitTillComplete=1
staad.SetSilentMode(False)
# status == 2 means success
Step 5 — Read results
out = staad.Output
# Verify first
blk_count = out.GetSteelDesignParameterBlockCount() # must be > 0
# Per-member full results
r = out.GetMemberSteelDesignResults(bid)
# Returns: (codeName, status, ratio, allowable, critLC, critPos, clause, section, forces[FX,MY,MZ], klr)
# status: 'PASS' or 'FAIL'; ratio > 1.0 = failure
# Quick ratio only
ratio = out.GetMemberSteelDesignRatio(bid) # -999=not designed, -1=no analysis
# Model-wide extremes
max_r = out.GetMemberSteelDesignMaxFailureRatio()
min_r = out.GetMemberSteelDesignMinFailureRatio()
Design Parameters
Assign parameters before running analysis:
design.AssignDesignParameter(brief_ref, paramName, paramValue, member_ids)
# Returns True on success and raises on failure
| Parameter | Description | Example |
|---|---|---|
| BEAM | Member is a beam | "1" |
| FYLD | Yield strength | "250" (MPa) |
| FU | Ultimate strength | "400" (MPa) |
| KY | Effective length factor Y | "0.85" |
| KZ | Effective length factor Z | "1.0" |
| LY | Unbraced length Y | "3000" (mm) |
| LZ | Unbraced length Z | "3000" (mm) |
| CB | Bending coefficient | "1.0" |
| UNL | Unsupported length | "6000" (mm) |
| TRACK | Output detail level | "2" |
| DMAX | Maximum section depth | "600" (mm) |
| DMIN | Minimum section depth | "200" (mm) |
What ships with it
2 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.
- 11d ago First seen · 128 lines · 173 tokens per session scan A 014497cc32ea
staad-steel-design is a skill published in the GitHub repository DP065U/STAAD-MCP (0 stars, last pushed 1mo ago), licensed MIT. It adds 173 tokens to every session and 1,307 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to staad-steel-design, 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…
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.
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…
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…