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 Cai-aa/CAE-Agent-Hub --skill composite-curing-simulationgit 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/composite-curing-simulation)<a href="https://agentmods.dev/skills/cai-aa/cae-agent-hub/composite-curing-simulation"><img src="https://agentmods.dev/badge/skills/cai-aa/cae-agent-hub/composite-curing-simulation.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.00063 | $0.02679 |
| Opus 5 | $0.00032 | $0.01340 |
| Sonnet 5 | $0.00013 | $0.00536 |
| Haiku 4.5 | $0.00006 | $0.00268 |
Grade A, and why
composite-curing-simulation 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 7d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Composite Curing Simulation
This is the master routing skill for composite material curing simulation. It provides an overview and routes to specialized sub-skills for each aspect of the workflow.
When to Invoke
- User requests composite curing simulation with mold
- User mentions "固化仿真", "脱模回弹", "模具", "铺层"
- User wants to change ply angles or ply count in a curing model
- User needs to run Abaqus with UMAT for composite materials
- User provides a reference INP with mold/contact/temperature and wants to replicate it
Critical: Mold Constraint vs No-Mold Constraint
This is the most important distinction in the curing model. Using the wrong constraint type produces physically incorrect results.
P8_mold (Correct — With Mold Contact + Demolding)
The correct model includes a TOOL part, friction contact pairs, and Model Change demolding in the sp step. This produces asymmetric springback deformation reflecting real physics.
| Feature | P8_mold (Correct) |
|---|---|
| TOOL part | Present (TOOL-1 instance) |
| Contact pair | com-surface (S1) ↔ tool-surface (S4+S6), HARD contact |
| Friction | Temperature-dependent: 0.45 → 0.2 → 0.169 |
| Curing constraint | Mold contact (TOOL U1=0, U2=0 via _PickedSet327/328) |
| Demolding | *Model Change, remove on TOOL elements + contact pair in sp step |
| Springback constraint | Set-2 (inner corner nodes): U1=U2=U3=0 via *Boundary, op=NEW |
| Pressure | 0.6 MPa on S2 (inner surface), removed in sp step |
| Springback contour | Asymmetric (max displacement at free edges) |
| Spring-in angle | Positive (0.5°-1.6°), physically correct |
P8_only (Incorrect — No Mold, ENCASTRE Constraint)
The incorrect model omits the TOOL part and uses ENCASTRE (full fixity) instead of mold contact. This produces center-symmetric deformation that does NOT reflect real curing physics.
| Feature | P8_only (Incorrect) |
|---|---|
| TOOL part | Absent |
| Contact pair | None |
| Friction | None |
| Curing constraint | ENCASTRE (U1=U2=U3=UR1=UR2=UR3=0) on inner surface |
| Demolding | None (no mold to remove) |
| Springback constraint | Same ENCASTRE remains |
| Springback contour | Center-symmetric (unphysical) |
| Spring-in angle | Does not reflect real physics |
What ships with it
18 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.
- analysis/curing-steps/SKILL.md 2.1 KB
- analysis/springback-analysis/SKILL.md 2.0 KB
- core/composite-curing/SKILL.md 8.8 KB
- execution/curing-job/SKILL.md 2.1 KB
- execution/socket-bridge/SKILL.md 2.7 KB
- modeling/composite-layup/SKILL.md 9.9 KB
- modeling/composite-mesh/SKILL.md 14 KB
- modeling/mold-geometry/SKILL.md 8.0 KB
- postprocessing/csv-export/SKILL.md 2.7 KB
- postprocessing/odb-extraction/SKILL.md 2.6 KB
- README.md 4.5 KB
- README.zh-CN.md 5.1 KB
- reference/curing-parameters/SKILL.md 2.3 KB
- setup/curing-bc/SKILL.md 5.5 KB
- setup/curing-contact/SKILL.md 5.5 KB
- setup/curing-load/SKILL.md 3.8 KB
- setup/curing-material/SKILL.md 3.3 KB
- setup/curing-temperature/SKILL.md 4.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.
- 7d ago First seen · 189 lines · 63 tokens per session scan A 1e85d85a0e14
composite-curing-simulation is a skill published in the GitHub repository Cai-aa/CAE-Agent-Hub (839 stars, last pushed 2d ago), licensed MIT. It adds 63 tokens to every session and 2,679 once invoked, about $0.0003 per session on Opus 5. 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…