write-methods-section

write-methods-section is a skill for Claude Code, Codex from equinor/neqsim. It costs 16 tokens per session (1,983 once invoked), scanned A, a copy of write_methods_section, Apache-2.0.

A guide for drafting the Methods section of a scientific paper about computational thermodynamics. It covers mathematical notation, algorithm steps, and how to describe benchmark tests; thermodynamics studies how heat, pressure, and matter behave.

In plain words
What is it for?
Use it to write Methods sections for flash-algorithm papers, explain phase-equilibrium calculations, document implementation details, and describe benchmark designs.
Why use it?
It gives technical work a clear structure so readers can understand the conditions, equations, implementation, and tests behind the results. This is useful when documenting changes for peer review or supplementary material.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to write Methods sections for flash-algorithm papers, explain phase-equilibrium calculations, document implementation details, and describe benchmark designs.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/equinor/neqsim/write-methods-section
Install

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.

Any agent
npx skills add equinor/neqsim --skill write-methods-section
Clone the repo
git clone --depth 1 https://github.com/equinor/neqsim

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for write-methods-section

README.md
[![agentmods](https://agentmods.dev/badge/skills/equinor/neqsim/write-methods-section/github.svg)](https://agentmods.dev/skills/equinor/neqsim/write-methods-section)
Your own site
<a href="https://agentmods.dev/skills/equinor/neqsim/write-methods-section"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/write-methods-section/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.

agentmods 80×15 button for write-methods-section

Your own site · 80×15
<a href="https://agentmods.dev/skills/equinor/neqsim/write-methods-section"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/write-methods-section.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 16 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,983 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 97% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00016 $0.01983
Opus 5.5 $0.00006 $0.00793
Sonnet 5.5 $0.00003 $0.00397
Haiku 4.5 $0.00002 $0.00198

Measured 27d ago against content hash 2078518e2057, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

write-methods-section 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 27d 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.

Origin

This is a copy

97% identical to write_methods_section — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.github/skills/write-methods-section/SKILL.md · 249 lines

How it starts

The opening of the file, as written. The whole thing — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Skill: Write Methods Section

Purpose

Draft a publication-quality Methods section for a computational thermodynamics paper. Includes mathematical notation, algorithm pseudocode, and benchmark design description.

When to Use

  • Drafting the Methods section of a flash algorithm paper
  • Documenting algorithmic changes for peer review
  • Writing supplementary material with implementation details

Methods Section Structure

A good Methods section for a flash algorithm paper has these subsections:

1. Thermodynamic Framework

State the phase equilibrium conditions:

## 2. Methods

### 2.1 Phase Equilibrium Conditions

At thermodynamic equilibrium, the fugacity of each component $i$ must be equal
across all phases:

$$f_i^V(T, P, \mathbf{y}) = f_i^L(T, P, \mathbf{x}) \quad \forall i = 1, \ldots, N_c$$

where $f_i^V$ and $f_i^L$ are the fugacities of component $i$ in the vapor and
liquid phases, $\mathbf{y}$ and $\mathbf{x}$ are the vapor and liquid mole
fraction vectors, and $N_c$ is the number of components.

The equilibrium ratio (K-value) is defined as:

$$K_i = \frac{y_i}{x_i} = \frac{\hat{\phi}_i^L(T, P, \mathbf{x})}{\hat{\phi}_i^V(T, P, \mathbf{y})}$$

where $\hat{\phi}_i$ denotes the fugacity coefficient.

2. Equation of State

Describe the EOS used:

### 2.2 Equation of State

Calculations in this work use the Soave-Redlich-Kwong (SRK) equation of state
\cite{Soave1972}:

$$P = \frac{RT}{V - b} - \frac{a(T)}{V(V + b)}$$

with classical van der Waals mixing rules:

$$a = \sum_i \sum_j x_i x_j (a_i a_j)^{1/2} (1 - k_{ij})$$

$$b = \sum_i x_i b_i$$

where $k_{ij}$ are binary interaction parameters.

3. Baseline Algorithm

Describe the algorithm being compared against:

### 2.3 Baseline TP Flash Algorithm

The baseline implementation follows the classical two-stage approach
\cite{Michelsen1982a, Michelsen1982b}:

**Stage 1: Successive Substitution (SS)**

Starting from Wilson K-value estimates:

$$K_i^{(0)} = \frac{P_{c,i}}{P} \exp\left[5.373(1 + \omega_i)\left(1 - \frac{T_{c,i}}{T}\right)\right]$$

the phase fraction $\beta$ is obtained from the Rachford-Rice equation:

$$g(\beta) = \sum_{i=1}^{N_c} \frac{z_i(K_i - 1)}{1 + \beta(K_i - 1)} = 0$$

K-values are updated by:

$$K_i^{(n+1)} = K_i^{(n)} \frac{\hat{\phi}_i^L(\mathbf{x}^{(n)})}{\hat{\phi}_i^V(\mathbf{y}^{(n)})}$$

This is repeated until convergence or a maximum of $N_{SS}$ iterations.

**Stage 2: Newton-Raphson (NR)**

If SS has not converged, the algorithm switches to Newton-Raphson using
Michelsen's u-variable formulation \cite{Michelsen1982b}:

$$u_i = \beta \cdot y_i$$

The residual vector is:

$$r_i = \ln \hat{\phi}_i^V(\mathbf{y}) - \ln \hat{\phi}_i^L(\mathbf{x})$$

and the Jacobian:

$$J_{ij} = \frac{\partial r_i}{\partial u_j}$$

The update is:

$$\mathbf{u}^{(n+1)} = \mathbf{u}^{(n)} - \alpha \mathbf{J}^{-1} \mathbf{r}$$

where $\alpha$ is a line search parameter (Armijo backtracking).

Read the full file on GitHub · 249 lines

Changes

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.

  1. 27d ago First seen · 249 lines · 16 tokens per session scan A 2078518e2057

Subscribe to this mod's changes

write-methods-section is a skill published in the GitHub repository equinor/neqsim (156 stars, last pushed today), licensed Apache-2.0. It adds 16 tokens to every session and 1,983 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 97% identical to write_methods_section, differing in 2 lines, and is treated as a copy.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens