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-stepsnpx skills add Cai-aa/CAE-Agent-Hub --skill curing-stepsgit 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-steps)<a href="https://agentmods.dev/skills/cai-aa/cae-agent-hub/curing-steps"><img src="https://agentmods.dev/badge/skills/cai-aa/cae-agent-hub/curing-steps.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.00657 |
| Opus 5 | $0.00000 | $0.00329 |
| Sonnet 5 | $0.00000 | $0.00131 |
| Haiku 4.5 | $0.00000 | $0.00066 |
Grade A, and why
curing-steps 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Curing Steps Analysis
Description
Configure 4-step curing analysis (vis, rub, glassy, sp) in Abaqus. Invoke when user needs curing step sequence, static step settings, or step-by-step curing process setup.
Content
The composite curing simulation uses 4 steps in sequence, all defined as *Static steps with nlgeom=NO.
Step Sequence
Step 1: vis (viscous state)
- Increment control: 0.1, 1., 1e-05, 0.5
- Temperature: 150°C
- Pressure: 0.6 MPa
- Friction: 0.45
- Tool BC: U1=0, U2=0
Step 2: rub (rubbery state)
- Increment control: 0.1, 1., 1e-05, 0.3
- Temperature: 180°C
- Pressure: 0.6 MPa
- Friction: 0.2 (taumax=0.55)
- Tool BC: continues from vis step
Step 3: glassy (glassy state)
- Increment control: 0.1, 1., 1e-05, 0.5
- Temperature: 25°C
- Pressure: No pressure
- Friction: 0.169
- Tool BC: continues from rub step
Step 4: sp (springback)
- Increment control: 0.1, 1., 1e-05, 0.5
- Temperature: 25°C
- Pressure: No pressure
- BC: Set-2 U1=U2=U3=0
- Model Change: removes contact + tool
Static Step Format
The *Static step uses the following format with initial increment, total time, min increment, and max increment:
*Static
initial_increment, total_time, min_increment, max_increment
Example for vis step:
*Static
0.1, 1., 1e-05, 0.5
Output Requests Per Step
Each step includes the following output requests:
*Output, field
*Node Output
CF, NT, RF, U
*Element Output, directions=YES
LE, PE, PEEQ, PEMAG, S, SDV, TEMP
*Contact Output
CDISP, CSTRESS
*Output, history, variable=PRESELECT
Restart Configuration
No restart output is written:
*Restart, write, frequency=0
Step Transitions
Loads and boundary conditions carry forward from one step to the next unless explicitly replaced with op=NEW. This means:
- Tool BCs applied in the vis step remain active through the glassy step
- Pressure applied in vis/rub steps is carried forward unless removed
- To replace all previous loads/BCs, use
op=NEWon the load or BC keyword
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 · 84 lines · 0 tokens per session scan A 1af8237ac96c
curing-steps 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 657 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…