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/load-gen-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/load-gen-api)<a href="https://agentmods.dev/skills/skyciv/skyciv-ai-skills/load-gen-api"><img src="https://agentmods.dev/badge/skills/skyciv/skyciv-ai-skills/load-gen-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/load-gen-api"><img src="https://agentmods.dev/badge/skills/skyciv/skyciv-ai-skills/load-gen-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.08824 |
| Opus 5.5 | $0.00000 | $0.03530 |
| Sonnet 5.5 | $0.00000 | $0.01765 |
| Haiku 4.5 | $0.00000 | $0.00882 |
Grade A, and why
load-gen-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 — 743 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Load Generator Agent Skill
You are an agent that retrieves wind speeds, snow loads, wind pressures, and seismic data for any location worldwide using the SkyCiv Load Generator API (standalone.loads namespace). This skill covers all functions, parameters, and design codes.
Prerequisite: Always begin a session with
standalone.loads.startas the first function (see "Session Start" below —S3D.session.startdoes not work here, despite what you may see suggested elsewhere). Seeskyciv-api-v3for auth, options, and the request/response envelope.
Calling this from inside an S3D App / left-menu panel? Get
authfrom the signed-in user withSKYCIV_UTILS.currentUser.getApiAuth()(returns{username, key}) — never prompt the user for an API key or cache one inlocalStoragefrom in-app code. See the "Authentication" section ofs3d-apps. The credential-collection UI described in the rootCLAUDE.mdis for standalone prototypes only, where there's no signed-in session to read from.
Session Start
Always open the session with standalone.loads.start, even in an app that also builds/solves an S3D model elsewhere:
{
"function": "standalone.loads.start",
"arguments": { "keep_open": false }
}
S3D.session.startdoes NOT work as the opener forstandalone.loads.*calls — this contradicts earlier guidance in this skill and inCLAUDE.mdclaiming it does. Confirmed directly against the live API: a call shaped[{S3D.session.start}, {standalone.loads.getLoads}]returnssession.startsucceeding butstandalone.loads.getLoadsfailing with a generic"The function 'standalone.loads.getLoads' could not be completed for an unknown reason"— not an auth error, not a clear "wrong session type" error, just a silent failure on the second call. The exact same request withstandalone.loads.startas the opener instead succeeds. If your app needs both an S3D model and a load-gen-api lookup, run them as two separate sessions/requests (each with its own matching*.startcall) rather than one combined envelope — do not assume the two namespaces can share a single session opener.
What ships with it
52 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.
- sample-api/loads.getLoads_as1170/input.json 2.6 KB
- sample-api/loads.getLoads_as1170/output.json 198 KB
- sample-api/loads.getLoads_asce_freestandingwall/input.json 1.8 KB
- sample-api/loads.getLoads_asce_freestandingwall/output.json 184 KB
- sample-api/loads.getLoads_asce_open_solar_panel/input.json 2.5 KB
- sample-api/loads.getLoads_asce_open_solar_panel/output.json 183 KB
- sample-api/loads.getLoads_asce_wind_only/input.json 475 B
- sample-api/loads.getLoads_asce_wind_only/output.json 182 KB
- sample-api/loads.getLoads_asce/input.json 1.3 KB
- sample-api/loads.getLoads_asce/output.json 184 KB
- sample-api/loads.getLoads_asce716_rooftop_equipment/input.json 1.0 KB
- sample-api/loads.getLoads_asce716_rooftop_equipment/output.json 78 KB
- sample-api/loads.getLoads_asce716_seismic_userdefined_params/input.json 1.6 KB
- sample-api/loads.getLoads_asce716_seismic_userdefined_params/output.json 182 KB
- sample-api/loads.getLoads_asce716_seismic/input.json 1.5 KB
- sample-api/loads.getLoads_asce716_seismic/output.json 190 KB
- sample-api/loads.getLoads_asce722_rooftop_equipment/input.json 1.0 KB
- sample-api/loads.getLoads_asce722_rooftop_equipment/output.json 77 KB
- sample-api/loads.getLoads_asce722_solar_panel_ground/input.json 1.1 KB
- sample-api/loads.getLoads_asce722_solar_panel_ground/output.json 78 KB
- sample-api/loads.getLoads_cfe_viento_gable/input.json 2.0 KB
- sample-api/loads.getLoads_cfe_viento_gable/output.json 183 KB
- sample-api/loads.getLoads_cfe_viento_pitched/input.json 878 B
- sample-api/loads.getLoads_cfe_viento_pitched/output.json 181 KB
- sample-api/loads.getLoads_en1991_germany/input.json 954 B
- sample-api/loads.getLoads_en1991_germany/output.json 84 KB
- sample-api/loads.getLoads_en1991_signboard/input.json 789 B
- sample-api/loads.getLoads_en1991_signboard/output.json 77 KB
- sample-api/loads.getLoads_en1991_uk/input.json 1.1 KB
- sample-api/loads.getLoads_en1991_uk/output.json 83 KB
- sample-api/loads.getLoads_is875/input.json 1.9 KB
- sample-api/loads.getLoads_is875/output.json 10.0 KB
- sample-api/loads.getLoads_nbcc/input.json 5.6 KB
- sample-api/loads.getLoads_nbcc/output.json 78 KB
- sample-api/loads.getLoads_nbcc2020_seismic/input.json 1.6 KB
- sample-api/loads.getLoads_nbcc2020_seismic/output.json 76 KB
- sample-api/loads.getLoads_nscp2015/input.json 1.1 KB
- sample-api/loads.getLoads_nscp2015/output.json 78 KB
- sample-api/loads.getLoads_nzs1170_seismic_bothdir/input.json 3.6 KB
- sample-api/loads.getLoads_nzs1170_seismic_bothdir/output.json 79 KB
- sample-api/loads.getSiteData_as1170/input.json 574 B
- sample-api/loads.getSiteData_as1170/output.json 1.2 KB
- sample-api/loads.getSiteData_asce716/input.json 456 B
- sample-api/loads.getSiteData_asce716/output.json 6.8 KB
- sample-api/loads.getSiteData_en1991_belgium/input.json 660 B
- sample-api/loads.getSiteData_en1991_belgium/output.json 916 B
- sample-api/loads.getSiteData_en1991_france/input.json 656 B
- sample-api/loads.getSiteData_en1991_france/output.json 1.1 KB
- sample-api/loads.getSiteData_en1991_germany/input.json 613 B
- sample-api/loads.getSiteData_en1991_germany/output.json 1.6 KB
- sample-api/loads.getSiteData_en1991_uk/input.json 808 B
- sample-api/loads.getSiteData_en1991_uk/output.json 1.8 KB
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 9307414ef9f8
- 15d ago Changed · +42 lines 7cd2b22659de
- 1mo ago Changed · +69 lines 1c8246c6c2b1
- 2mo ago First seen · 632 lines · 0 tokens per session scan A 24954d4ff593
load-gen-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 8,824 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…