staad-errors

staad-errors is a skill for Claude Code, Codex from DP065U/STAAD-MCP. It costs 113 tokens per session (1,440 once invoked), scanned A, a copy of staad-errors, MIT.

A skill for handling errors from OpenSTAAD, the programming interface for STAAD.Pro structural-engineering software. It explains return codes, uncaught exceptions, sandbox limits, COM failures, and version compatibility.

In plain words
What is it for?
Use it when running OpenSTAAD operations, reading negative return codes, handling bulk operations, or diagnosing errors caused by an older STAAD.Pro version.
Why use it?
It helps an agent interpret failures and choose when to stop an operation, continue with a fallback, or skip one bad item in a larger task.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when running OpenSTAAD operations, reading negative return codes, handling bulk operations, or diagnosing errors caused by an older STAAD.Pro version.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/dp065u/staad-mcp/staad-errors
Install

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.

Any agent
npx skills add DP065U/STAAD-MCP --skill staad-errors
Clone the repo
git clone --depth 1 https://github.com/DP065U/STAAD-MCP

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for staad-errors

README.md
[![agentmods](https://agentmods.dev/badge/skills/dp065u/staad-mcp/staad-errors/github.svg)](https://agentmods.dev/skills/dp065u/staad-mcp/staad-errors)
Your own site
<a href="https://agentmods.dev/skills/dp065u/staad-mcp/staad-errors"><img src="https://agentmods.dev/badge/skills/dp065u/staad-mcp/staad-errors/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.

agentmods 80×15 button for staad-errors

Your own site · 80×15
<a href="https://agentmods.dev/skills/dp065u/staad-mcp/staad-errors"><img src="https://agentmods.dev/badge/skills/dp065u/staad-mcp/staad-errors.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 113 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,440 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00113 $0.01440
Opus 5.5 $0.00045 $0.00576
Sonnet 5.5 $0.00023 $0.00288
Haiku 4.5 $0.00011 $0.00144

Measured 1mo ago against content hash 562b5025fb4c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

staad-errors 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 1mo 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.

Origin

This is a copy

100% identical to staad-errors — 55 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.

src/openstaad_mcp/staad_skills/staad-errors/SKILL.md · 111 lines

How it starts

The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.

STAAD.Pro Error Handling

Errors Are Reported Automatically

execute_code wraps your whole script in a top-level handler: any uncaught exception is captured and returned as success: false with the (sanitized) error message plus whatever you printed before it. You do NOT need try/except just to report a failure — let it propagate and read the error from the tool result.

Use try/except inside a script only when it changes control flow, e.g.:

  • skipping a bad item inside a bulk loop so the rest keep processing
  • providing a fallback value (e.g. version-gated features) and continuing

Sandbox Limitation

In the MCP sandbox, import is blocked. You cannot import typed exception classes from openstaadpy.os_analytical.oserrors. Instead, catch generic Exception and inspect the message or code.

Clear COM Errors

The openstaadpy wrapper wraps COM objects in a proxy layer that turns cryptic COM failures into actionable messages. If a COM method is missing or fails, the error typically tells you to update STAAD.Pro to the latest version — this usually means the connected STAAD instance is older than the function requires (see staad-core → Version Compatibility), not a coding mistake.

Return Contracts

Many methods raise on failure — call them directly and let execute_code surface any error. This applies to the Assign* methods and the support create/assign/query/delete methods, which return True on success and raise on failure:

prop.AssignBeamProperty(beam_ids, prop_id)   # True on success; raises on failure

Some query/getter methods still return negative integers on error instead of raising — for those, check the sign:

shape = prop.GetShapeCode(country, name)
if isinstance(shape, int) and shape < 0:
    print(f"Section not found (code {shape})")

Robust Model Building Pattern

Catch per-item inside a loop so one bad entity doesn't abort the whole batch:

geo = staad.Geometry

def safe_add_beam(start, end):
    try:
        return geo.AddBeam(start, end)
    except Exception as e:
        print(f"  Beam ({start}->{end}) skipped: {e}")
        return None

for s, e in [(1, 2), (2, 3), (3, 99)]:
    bno = safe_add_beam(s, e)
    if bno:
        print(f"Added beam {bno}")

Read the full file on GitHub · 111 lines

Files

What ships with it

1 file 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.

Changes

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.

  1. 1mo ago First seen · 111 lines · 113 tokens per session scan A 562b5025fb4c

Subscribe to this mod's changes

staad-errors is a skill published in the GitHub repository DP065U/STAAD-MCP (0 stars, last pushed 3mo ago), licensed MIT. It adds 113 tokens to every session and 1,440 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to staad-errors, differing in 55 lines, and is treated as a copy.

Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

deck-retro

Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…

asheshgoplani/agent-deck · 86 tokens

incident-response-incident-response

Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.

rmyndharis/antigravity-skills · 36 tokens

cwv-optimizer

Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…

adobe/skills · 112 tokens