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 agentmods add skills/cai-aa/cae-agent-hub/curing-loadnpx skills add Cai-aa/CAE-Agent-Hub --skill curing-loadgit clone --depth 1 https://github.com/Cai-aa/CAE-Agent-HubWrote 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/cai-aa/cae-agent-hub/curing-load)<a href="https://agentmods.dev/skills/cai-aa/cae-agent-hub/curing-load"><img src="https://agentmods.dev/badge/skills/cai-aa/cae-agent-hub/curing-load.svg" alt="Measured on agentmods" 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.00000 | $0.00886 |
| Opus 5 | $0.00000 | $0.00443 |
| Sonnet 5 | $0.00000 | $0.00177 |
| Haiku 4.5 | $0.00000 | $0.00089 |
Grade A, and why
curing-load 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 6d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Curing Load Setup
Description
Define pressure loads for composite curing simulation. Invoke when user needs to apply pressure on composite surface during curing.
Pressure Application Surface
Pressure is applied on the inner surface of the composite, NOT the outer/contact surface.
- _PickedSurf337 (S2 of composite): Pressure application surface (inner face).
- The contact surface (com-surface, S1) is on the opposite face and is NOT used for pressure application.
Surface Identification
- S1: Outer face of composite (contact surface with mold) - used for contact pair.
- S2: Inner face of composite (opposite to contact face) - used for pressure application.
The pressure represents the autoclave pressure applied to the composite during curing. It is applied on the inner surface so that it pushes the composite against the mold, ensuring proper contact and compaction.
Load Definition
The pressure load is defined using the *Dsload (distributed surface load) keyword:
*Dsload
_PickedSurf337, P, 0.6
- _PickedSurf337: The surface name (inner face of composite, S2).
- P: Pressure load type (normal pressure on the surface).
- 0.6: Pressure magnitude = 0.6 MPa (typical autoclave curing pressure).
Pressure Application Schedule
The pressure is applied only during specific steps of the curing cycle:
vis Step (Viscous State)
*Dsload
_PickedSurf337, P, 0.6
- Pressure = 0.6 MPa applied during the viscous (high-temperature) step.
- The pressure compacts the composite against the mold while the resin is in a low-viscosity state.
rub Step (Rubbery State)
*Dsload
_PickedSurf337, P, 0.6
- Pressure = 0.6 MPa maintained during the rubbery step.
- The pressure continues to hold the composite against the mold as the material transitions to a rubbery state.
glassy Step (Glassy State)
No pressure is applied in the glassy step. The pressure is implicitly removed because it is not re-specified. Abaqus carries forward loads from previous steps unless they are modified or removed.
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.
- 6d ago First seen · 91 lines · 0 tokens per session scan A ca527c5dad41
curing-load is a skill published in the GitHub repository Cai-aa/CAE-Agent-Hub (839 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 886 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-30.
Other skills, from other repositories
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
matlab
Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.
exploratory-data-analysis
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…
phylogenetics
Build and analyze phylogenetic trees using MAFFT (multiple alignment), IQ-TREE 2 (maximum likelihood), and FastTree (fast NJ/ML). Visualize with ETE3 or FigTree. For evolutionary analysis, microbial genomics, viral phylodynamics, protein family analysis, and molecular clock studies.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…