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 equinor/neqsim-community-skills --skill fired-heater-duty-screeninggit clone --depth 1 https://github.com/equinor/neqsim-community-skillsWrote 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/equinor/neqsim-community-skills/fired-heater-duty-screening)<a href="https://agentmods.dev/skills/equinor/neqsim-community-skills/fired-heater-duty-screening"><img src="https://agentmods.dev/badge/skills/equinor/neqsim-community-skills/fired-heater-duty-screening/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/equinor/neqsim-community-skills/fired-heater-duty-screening"><img src="https://agentmods.dev/badge/skills/equinor/neqsim-community-skills/fired-heater-duty-screening.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.00066 | $0.01185 |
| Opus 5 | $0.00033 | $0.00593 |
| Sonnet 5 | $0.00013 | $0.00237 |
| Haiku 4.5 | $0.00007 | $0.00119 |
Grade A, and why
neqsim-fired-heater-duty-screening 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 12d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fired Heater Duty Screening
Use this skill for public, educational fired-heater screening. It estimates the process duty, the fired duty, the fuel-gas rate, and the average radiant-section heat flux using open energy-balance relations so an agent can scope a fired-heater study and check the radiant flux against a public guideline before detailed thermal design.
When to Use
- When a user asks roughly what fired duty and fuel rate a heater needs.
- When an agent needs a quick radiant-flux check to scope a fired-heater study.
- When examples must run without confidential heater designs, vendor data, or company specs.
Inputs
mass_flow: process mass flow in kg/s.specific_heat: process-fluid specific heat in kJ/(kg K).inlet_temperature: process inlet temperature in kelvin.outlet_temperature: process outlet temperature in kelvin.thermal_efficiency: heater thermal efficiency, default 0.85.fuel_heating_value: fuel lower heating value in MJ/kg, default 46.0.radiant_area: radiant-section tube surface area in m2.allowable_radiant_flux: allowable average radiant flux in kW/m2, default 37.0.
Outputs
process_duty_kw: process absorbed dutyQ.fired_duty_kw: fired duty from the efficiency.fuel_rate_kg_s: fuel-gas mass rate.average_radiant_flux_kw_m2: process duty divided by radiant area.flux_ratio: ratio of average radiant flux to the allowable flux.fired_heater_warning:ok,watch, orhigh-flux.assumptions: public assumptions used by the placeholder model.
Engineering Method
The Python class FiredHeaterDutyModel uses open energy-balance relations only:
- the process duty uses
Q = mass_flow * specific_heat * (T_out - T_in). - the fired duty uses
Q_fired = Q / thermal_efficiency. - the fuel rate uses
fuel = Q_fired / fuel_heating_value. - the average radiant flux uses
Q / radiant_areaand is compared to a public guideline.
This is educational and screening-only logic. It uses a constant specific heat, treats all process duty as absorbed in the radiant section for the flux estimate, and does not model convection-section split, tube-wall temperature, flame and bridgewall temperature, draft, or emissions. Typical public average radiant fluxes are about 30 to 37 kW/m2. It is not a replacement for validated fired-heater design (for example API 560) and a qualified review.
What ships with it
6 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.
- 12d ago First seen · 111 lines · 66 tokens per session scan A 21152a2b9a42
neqsim-fired-heater-duty-screening is a skill published in the GitHub repository equinor/neqsim-community-skills (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 66 tokens to every session and 1,185 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-31.
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…