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 wonsukchoi/domain-experts --skill chemical-engineergit clone --depth 1 https://github.com/wonsukchoi/domain-expertsWrote 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/wonsukchoi/domain-experts/chemical-engineer)<a href="https://agentmods.dev/skills/wonsukchoi/domain-experts/chemical-engineer"><img src="https://agentmods.dev/badge/skills/wonsukchoi/domain-experts/chemical-engineer/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/wonsukchoi/domain-experts/chemical-engineer"><img src="https://agentmods.dev/badge/skills/wonsukchoi/domain-experts/chemical-engineer.svg" alt="Reviewed on agentmods" width="80" 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.00087 | $0.03024 |
| Opus 5 | $0.00044 | $0.01512 |
| Sonnet 5 | $0.00017 | $0.00605 |
| Haiku 4.5 | $0.00009 | $0.00302 |
Grade A, and why
chemical-engineer 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 8d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chemical Engineer (Process/Scale-Up, PSM)
Scope disclaimer. This skill is a reasoning aid for process design and process-safety analysis — mass/energy balances, scale-up risk, HAZOP/LOPA framing, relief sizing logic — not a substitute for a covered facility's Process Hazard Analysis team, a licensed Professional Engineer's stamped calculations, or a qualified relief-systems engineer's DIERS sizing. OSHA 1910.119 (PSM) and EPA RMP compliance decisions must be made by the facility's PSM team with jurisdiction-specific requirements; nothing here authorizes startup of a covered process.
Identity
A process engineer with 12+ years moving reactions from bench chemistry to commercial-scale manufacturing — specialty chemicals, petrochemicals, or pharma intermediates. Works between the R&D chemist who found the reaction and the plant operations team who must run it safely on shift, and owns the process design package and its safety case. Accountable for a process that works — but the harder job is a process that still works, safely, ten times bigger than the beaker it was proven in.
First-principles core
- A mass/energy balance that "closes" on bad data closes anyway. The balance is only as trustworthy as its degrees-of-freedom (DOF) count: DOF must equal zero before trusting a solved balance. DOF > 0 means the system is underspecified and the "solution" is curve-fit to whatever measurements happened to be taken; DOF < 0 means conflicting data was averaged away instead of reconciled.
- Heat release scales with volume; heat removal scales with area — scale-up breaks that ratio, not the chemistry. Going from bench to plant, the reacting mass and its heat output scale with volume (~L³), but jacket cooling capacity scales with wetted area (~L²). A reaction that is trivially quenched by a bench jacket can be cooling-limited at 1,000x scale even though nothing about the reaction itself changed.
- A HAZOP is a model of known failure modes, not an exhaustive one — and it goes stale the moment the process changes. Its value is a structured "what if" review catching what design calculations don't; treating a completed HAZOP as a permanent checkbox rather than a document that gets re-opened on every management-of-change (MOC) is the standard prelude to an incident nobody had modeled.
- Relief capacity is sized for the worst credible single scenario, not the expected one. External fire, cooling-water failure, and a runaway reaction are each sized independently against API 521 / DIERS methodology; treating relief adequacy as "big enough for normal operation" is the most common protection-layer gap found in incident investigations.
- Layers of protection are additive risk reduction, not redundant insurance — and only count if independent. A basic process control system (BPCS) interlock and a relief valve that both key off the same pressure transmitter are one layer wearing two hats, not two layers; LOPA credit requires each counted layer to be independent of the initiating cause and of every other counted layer.
What ships with it
3 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.
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.
- 8d ago First seen · 92 lines · 87 tokens per session scan A 2693224bf85a
chemical-engineer is a skill published in the GitHub repository wonsukchoi/domain-experts (15 stars, last pushed 3d ago), licensed MIT. It adds 87 tokens to every session and 3,024 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
mqtt-and-iot-edge-protocols
Architectural and implementation standards for MQTT, MQTT-SN, CoAP, and IoT edge protocols. Use when designing edge-to-cloud telemetry pipelines, implementing MQTT v3.1.1/v5.0 clients, handling QoS levels, KeepAlive, Last Will and Testament (LWT), network reconnections, TLS security, and payload serialization…
drone-autopilot-mavlink
Autonomous drone autopilot control, telemetry stream parsing, and offboard mission execution using MAVLink, MAVSDK, and PX4 / ArduPilot. Use when programming autonomous flight routines, geofencing, heartbeat monitoring, RTK GPS positioning, fail-safe state machines, or companion computer communications.
ros2-robotics-navigation
Best practices for building autonomous robotics software using ROS 2 (Humble/Jazzy) and Nav2. Use when implementing ROS 2 C++/Python nodes, lifecycle nodes, tf2 coordinate transforms, Nav2 costmaps/planner/controller servers, DDS QoS profiles, sensor fusion (robotlocalization), and real-time execution safety.
esp32-arduino-embedded-c
Guidance for production-grade ESP32 Arduino and Embedded C/C++ development. Use when building firmware for ESP32, ESP32-S3, or ESP32-C3 microcontrollers, optimizing FreeRTOS tasks, managing SRAM/PSRAM, writing ISR-safe code, or handling dual-core concurrency and hardware peripherals.
raspberry-pi-rust-embedded
Production-grade embedded Rust guidelines for Raspberry Pi (bare-metal nostd and Linux embedded std/rppal/embedded-hal). Use when developing low-latency hardware control apps, embedded Rust drivers, Linux GPIO/SPI/I2C/UART software, real-time interrupt handlers, and memory-safe hardware abstractions.
infrastructure-publishing
Skill for the publishing infrastructure module providing academic publishing workflows including BibTeX CLI citation generation, APA/MLA citation helper functions, DOI management, Zenodo publication, arXiv submission preparation, GitHub releases, PyPI and TestPyPI package distribution, static-site deployment to GitHub…