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 marcinfinitesimal533/Claude-skills-for-Computational-Designers --skill interoperabilitygit clone --depth 1 https://github.com/marcinfinitesimal533/Claude-skills-for-Computational-DesignersWrote 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/marcinfinitesimal533/claude-skills-for-computational-designers/interoperability)<a href="https://agentmods.dev/skills/marcinfinitesimal533/claude-skills-for-computational-designers/interoperability"><img src="https://agentmods.dev/badge/skills/marcinfinitesimal533/claude-skills-for-computational-designers/interoperability/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/marcinfinitesimal533/claude-skills-for-computational-designers/interoperability"><img src="https://agentmods.dev/badge/skills/marcinfinitesimal533/claude-skills-for-computational-designers/interoperability.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.00038 | $0.12873 |
| Opus 5 | $0.00019 | $0.06437 |
| Sonnet 5 | $0.00008 | $0.02575 |
| Haiku 4.5 | $0.00004 | $0.01287 |
Grade A, and why
interoperability scanned grade A with 1 finding 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 12d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
response = requests.get(url, headers=headers) This is a copy
100% identical to interoperability — 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 — 1,050 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Interoperability for AEC Computational Design
1. The Interoperability Challenge in AEC
1.1 Why Interoperability Matters
Interoperability -- the ability to exchange data between software tools without loss of meaning, geometry, or relationships -- is the single most critical infrastructure problem in the AEC industry. Every building project involves dozens of software tools, hundreds of files, and thousands of data exchanges. When those exchanges fail, the consequences are measured in millions of dollars and months of delay.
The AEC industry loses an estimated $15.8 billion annually in the United States alone due to inadequate interoperability (NIST GCR 04-867). This figure accounts for redundant data entry, manual format conversion, error correction from data loss, and delayed decision-making caused by information silos.
Unlike the manufacturing or aerospace industries, which converged on STEP/IGES decades ago, the AEC sector remains fragmented across proprietary ecosystems. Autodesk, Bentley, Trimble, Nemetschek, and dozens of smaller vendors each maintain walled gardens with varying degrees of openness. The result is a landscape where a single design decision may need to be re-entered into five or more tools before it reaches a construction site.
1.2 Single-Source-of-Truth vs. Federated Model Approaches
Single-Source-of-Truth (SSOT):
- One authoritative model from which all views and deliverables derive
- Revit-centric workflows often attempt this, with one central model containing architecture, structure, and MEP
- Advantages: no synchronization burden, clear ownership, simpler version control
- Disadvantages: tool lock-in, performance limits at scale, inability to leverage best-of-breed tools
- Practical limit: SSOT breaks down beyond approximately 200-300 MB models or when disciplines require specialized solvers
Federated Model Approach:
- Multiple discipline-specific models linked through coordination mechanisms
- Each discipline uses its optimal tool (Revit for documentation, Rhino for complex geometry, Tekla for steel detailing, ETABS for structural analysis)
- Coordination via shared coordinates, reference planes, and clash detection (Navisworks, Solibri, BIMcollab)
- Advantages: best-of-breed tooling, team autonomy, distributed workload
- Disadvantages: synchronization overhead, version mismatch risk, coordinate alignment complexity
- Industry trend: federated approaches are winning, especially with Speckle and IFC enabling richer exchange
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.
- 12d ago First seen · 1,050 lines · 38 tokens per session scan A ef8d1cc481a7
interoperability is a skill published in the GitHub repository marcinfinitesimal533/Claude-skills-for-Computational-Designers (2 stars, last pushed 2d ago), licensed MIT. It adds 38 tokens to every session and 12,873 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to interoperability, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
interoperability
File format encyclopedia, data exchange strategies, API integration patterns, Grasshopper-to-Revit pipelines, Rhino.Inside workflows, Speckle data streams, and schema mapping for AEC computational design.
api-rate-limit-handler
Implement bounded, idempotency-aware API throttling, backoff, and retry handling for 429 and transient 5xx responses.
nextjs-pages-router
Set up tRPC in Next.js Pages Router with createNextApiHandler, createTRPCNext, withTRPC HOC, SSR via ssr option and ssrPrepass, SSG via createServerSideHelpers with getStaticProps, and server-side helpers for getServerSideProps prefetching.
non-json-content-types
Handle FormData, file uploads, Blob, Uint8Array, and ReadableStream inputs in tRPC mutations. Use octetInputParser from @trpc/server/http for binary data. Route non-JSON requests with splitLink and isNonJsonSerializable() from @trpc/client. FormData and binary inputs only work with mutations (POST).
middlewares
Create and compose tRPC middleware with t.procedure.use(), extend context via opts.next({ ctx }), build reusable middleware with .concat() and .unstablepipe(), define base procedures like publicProcedure and authedProcedure. Access raw input with getRawInput(). Logging, timing, OTEL tracing patterns.
server-side-calls
Call tRPC procedures directly from server code using t.createCallerFactory() and router.createCaller(context) for integration testing, internal server logic, and custom API endpoints. Catch TRPCError and extract HTTP status with getHTTPStatusCodeFromError(). Error handling via onError option.