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

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.

agentmods
npx agentmods add skills/dp065u/staad-mcp/staad-errors
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.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.svg" alt="Measured on agentmods" 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. Scan, not verified.
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 $0.00113 $0.01440
Opus 5 $0.00056 $0.00720
Sonnet 5 $0.00023 $0.00288
Haiku 4.5 $0.00011 $0.00144

Measured 3d ago against content hash 562b5025fb4c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 3d 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 — 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.

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. 3d 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 1mo ago), licensed MIT. It adds 113 tokens to every session and 1,440 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to staad-errors, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens