Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/skyciv/skyciv-ai-skillsnpx agentmods add skills/skyciv/skyciv-ai-skills/s3d-apiWrote 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/skyciv/skyciv-ai-skills/s3d-api)<a href="https://agentmods.dev/skills/skyciv/skyciv-ai-skills/s3d-api"><img src="https://agentmods.dev/badge/skills/skyciv/skyciv-ai-skills/s3d-api/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/skyciv/skyciv-ai-skills/s3d-api"><img src="https://agentmods.dev/badge/skills/skyciv/skyciv-ai-skills/s3d-api.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00000 | $0.14888 |
| Opus 5.5 | $0.00000 | $0.05955 |
| Sonnet 5.5 | $0.00000 | $0.02978 |
| Haiku 4.5 | $0.00000 | $0.01489 |
Grade A, and why
s3d-api 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 14d 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.
How it starts
The opening of the file, as written. The whole thing — 1,345 lines — stays where its author put it; the contents beside it link to each section on GitHub.
S3D Agent Skill
You are an agent that builds, analyses, and queries SkyCiv Structural 3D (S3D) structural models via the SkyCiv API. This skill covers the full s3d_model JSON schema and every function in the S3D.model, S3D.results, S3D.file, and S3D.SB namespaces, plus the S3D.design member/RC design checks.
Designing members? Use
S3D.design.member.checkfirst. If the design code is in the supported list, design the members in the solved model withS3D.design.member.check, not with arun-quick-designcalculator. Only use Quick Design when Member Design can't do the job. See S3D.design Functions.
Prerequisite: Always begin a session with
S3D.session.startas the first function. Seeskyciv-api-v3for auth, options, and the request/response envelope.
The s3d_model Object
The s3d_model is the JSON representation of a structural model. It is passed to S3D.model.set.
{
"settings": { ... },
"nodes": { ... },
"members": { ... },
"plates": { ... },
"meshed_plates": { ... },
"sections": { ... },
"materials": { ... },
"supports": { ... },
"settlements": { ... },
"point_loads": { ... },
"moments": { ... },
"distributed_loads": { ... },
"pressures": { ... },
"area_loads": { ... },
"member_prestress_loads": { ... },
"thermal_loads": { ... },
"self_weight": { ... },
"load_combinations": { ... },
"load_cases": { ... },
"load_combination_settings": { ... },
"nodal_masses": { ... },
"spectral_loads": { ... },
"moving_loads": { ... },
"suppress": { ... },
"groups": { ... },
"gridlines_and_elevations": [ ... ]
}
All objects use integer-keyed dictionaries (e.g. "1": { ... }, "2": { ... }), except gridlines_and_elevations, which is a plain array.
Tip: To inspect a model as JSON, open it in SkyCiv S3D and use File → Export → SkyCiv File (JSON for API). To test JSON, use File → Import → SkyCiv File (JSON for API).
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.
- 14d ago Changed · +49 lines f4cb36c2a07f
- 24d ago Changed · +97 lines 59b6672a4956
- 1mo ago Changed · +162 lines 7bc4028d1827
- 2mo ago First seen · 1,037 lines · 0 tokens per session scan A 6309c67684ac
s3d-api is a skill published in the GitHub repository skyciv/skyciv-ai-skills (11 stars, last pushed 15d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 14,888 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
adaptyv
Uses the Adaptyv Bio Foundry API and Python SDK to design protein characterization experiments, estimate costs, submit sequences, monitor laboratory progress, and retrieve results. Applies to Adaptyv Foundry, its target catalog, binding screening and affinity assays, thermostability, expression, fluorescence, epitope…
labarchive-integration
Integrates with the official LabArchives ELN REST-like API and Inventory API v1. Supports regional endpoint selection, signed-request construction, user authorization and UID flows, local LA container validation, and verified LabArchives integration workflows.
benchling-integration
Benchling Python SDK and REST API integration for registry entities, inventory, ELN entries, workflows, Benchling Apps, and Data Warehouse queries. Use when automating lab data with benchling-sdk or the v2 API.
earth2studio-create-datasource
Create and validate Earth2Studio data source wrappers (DataSource, ForecastSource, DataFrameSource, ForecastFrameSource) from remote stores. Do NOT use for fetching data with existing sources, model inference, or installation tasks.
assembling-fhir-bundles
Package multiple FHIR R4 resources produced from OpenMed output into a single valid transaction Bundle ready to POST to an EHR, using OpenMed's verified bundle assembler openmed.clinical.exporters.fhir.tobundle. Covers deterministic urn:uuid fullUrls, automatic in-Bundle reference rewriting, request blocks…
exporting-bulk-fhir
Kick off and harvest a FHIR Bulk Data $export (system-, group-, or patient-level) and stream the resulting NDJSON into a batch OpenMed de-identification + NER pipeline at cohort scale. Covers the async kickoff (Prefer respond-async) -> poll Content-Location -> download NDJSON flow, the Bulk Data Access IG, type/since…