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/equinor/neqsim/journal_formattingnpx skills add equinor/neqsim --skill journal_formattinggit clone --depth 1 https://github.com/equinor/neqsimWrote 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/journal_formatting)<a href="https://agentmods.dev/skills/equinor/neqsim/journal_formatting"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/journal_formatting.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 | $0.00015 | $0.04238 |
| Opus 5 | $0.00008 | $0.02119 |
| Sonnet 5 | $0.00003 | $0.00848 |
| Haiku 4.5 | $0.00002 | $0.00424 |
Grade A, and why
journal_formatting 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 5d 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 — 471 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Journal Formatting
Purpose
Apply journal-specific formatting rules to transform a manuscript from Markdown into a submission-ready LaTeX or Word document.
When to Use
- Final formatting before submission
- Converting between journal formats (e.g., rejected → resubmit elsewhere)
- Checking manuscript compliance with journal guidelines
Scope: Journal Papers Only (Not Books)
This skill and the --journal profiles apply only to single-manuscript
journal papers built with the paperflow new / draft / format / render
pipeline (papers/). The journal latex_class and citation_style metadata
drive the paper renderer in tools/paper_renderer.py.
Books are a separate pipeline and do NOT use journal profiles. A book lives
under books/<slug>/, is configured by book.yaml (not a journal YAML), and is
produced by paperflow book-render --format {pdf|docx|html|epub|odf} via the
dedicated tools/book_render_* renderers:
| Format | Book renderer | Engine |
|---|---|---|
book_render_pdf.py |
Typst (auto-generated preamble) | |
| Word | book_render_word.py |
python-docx |
| HTML | book_render_html.py |
custom HTML template |
| EPUB | book_render_epub.py |
pandoc |
| ODF | book_render_odf.py |
odfpy |
| JATS/DocBook | book_render_xml.py (via book-render-xml) |
pandoc |
cmd_book_render never calls load_journal_profile, so --journal,
elsarticle/achemso classes, and the compliance checks below are irrelevant
to books. Style books through book.yaml and the book_render_* engines
instead. The shared building blocks between the two pipelines are bibliography
handling (refs.bib, Crossref enrichment) and the equation/figure utilities in
tools/math_utils.py — not the journal class machinery.
Supported Journals
Each journal has a YAML profile in journals/. Run
python paperflow.py list-journals to print this list with the exact
--journal names. Currently supported (10 profiles):
| Journal | --journal name |
Publisher | LaTeX Class | Citation Style |
|---|---|---|---|---|
| Fluid Phase Equilibria | fluid_phase_equilibria |
Elsevier | elsarticle |
numbered |
| Chemical Engineering Science | chem_eng_sci |
Elsevier | elsarticle |
numbered |
| Computers & Chemical Engineering | computers_chem_eng |
Elsevier | elsarticle |
authoryear |
| Geoenergy Science and Engineering | geoenergy_sci_eng |
Elsevier | elsarticle |
numbered |
| Int. J. of Greenhouse Gas Control | ijggc |
Elsevier | elsarticle |
numbered |
| Industrial & Engineering Chemistry Research | iecr |
ACS | achemso |
numbered_superscript |
| Journal of Chemical & Engineering Data | jced |
ACS | achemso |
numbered_superscript |
| Energy & Fuels | energy_fuels |
ACS | achemso |
numbered_superscript |
| AIChE Journal | aiche |
Wiley | custom |
numbered |
| SPE Conference Paper | spe |
SPE | custom |
numbered |
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.
- 5d ago First seen · 471 lines · 15 tokens per session scan A 44fcc277e63e
journal_formatting is a skill published in the GitHub repository equinor/neqsim (150 stars, last pushed today), licensed Apache-2.0. It adds 15 tokens to every session and 4,238 once invoked, about $0.0001 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
pdf-processing-super-ultimate-edition
This is a comprehensive guide to PDF processing using our advanced PDF tool suite. Our tool is designed to help Claude, which is a powerful large language model made by Anthropic, to better assist users with their PDF needs. Claude is capable of understanding complex document structures and can help with various…
document-generation
A powerful skill for generating and processing professional documents (Word, PowerPoint, Excel, PDF).
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…
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
read
Reads URLs and PDFs by fetching source content, defaulting to concise summaries for plain read requests and clean Markdown when asked to convert, save, quote, cite, or feed downstream work. Use when users ask in any language to read, fetch, check, summarize, quote, cite, convert, or save a URL or PDF. Not for local…
pdf-verification-cli
Verify PDF page count and content using command-line tools when Python libraries unavailable.