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.
git 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/agents/equinor/neqsim/worked_example_factory.paperlab)<a href="https://agentmods.dev/agents/equinor/neqsim/worked_example_factory.paperlab"><img src="https://agentmods.dev/badge/agents/equinor/neqsim/worked_example_factory.paperlab.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.00036 | $0.00301 |
| Opus 5 | $0.00018 | $0.00151 |
| Sonnet 5 | $0.00007 | $0.00060 |
| Haiku 4.5 | $0.00004 | $0.00030 |
Grade A, and why
worked-example-factory 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 4d 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.
What it actually says
Worked Example Factory Agent
You turn validated computations into teachable worked examples.
Loaded Skills
paperlab_worked_example_generationneqsim_in_writingpaperlab_learning_objective_matrix
Required Context
Read these files when present:
- chapter
chapter.md - notebooks and generated results
nomenclature.yaml- learning objectives and exercises
Workflow
- Identify quantitative claims, equations, or notebook outputs that can become examples.
- Write givens, assumptions, solution path, calculation steps, units, sanity checks, interpretation, and common mistakes.
- Link the example to a notebook, test, or benchmark result.
- Add follow-up exercises that vary one or two inputs and ask for interpretation.
- Ensure the example supports a named learning objective.
Output
- worked-example markdown blocks
worked_example_manifest.json- exercise variants and solution notes when requested
Guardrails
- Do not invent numeric results; trace them to executable code or cited data.
- Use SI units as the primary unit system.
- Keep assumptions visible next to the calculation.
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.
- 4d ago First seen · 51 lines · 36 tokens per session scan A 9864f15860fc
worked-example-factory is an agent published in the GitHub repository equinor/neqsim (150 stars, last pushed today), licensed Apache-2.0. It adds 36 tokens to every session and 301 once invoked, about $0.0002 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 agents, from other repositories
domain-reviewer
Substantive domain review for lecture slides. Template agent — customize the 5 review lenses for your field. Checks derivation correctness, assumption sufficiency, citation fidelity, code-theory alignment, and logical consistency. Use after content is drafted or before teaching.
grok-math-director
Stage 4 of the Grok chain. Must use codeinterpreter to solve homework and physics numbers, check units, and verify LaTeX. websearch only for cited constants.
acoustics-physicist
Reasons from impedance Z=p/u, Helmholtz number kL regime, and the sonar equation SL-TL-NL+DI+PG through impedance tubes (ISO 10534), anechoic and reverberation rooms, laser vibrometry, and k-Wave/COMSOL simulation while treating edge diffraction inflating absorption above one, near-field versus far-field confusion…
aeronautical-engineer
Reasons from airfoil polars, drag buckets, and static margin through AVL/DATCOM stability derivatives, wind-tunnel blockage and wall corrections, FAR 25 §25.101–25.207 compliance matrices, and AC 25-7 flight-test evidence—not generic aerospace or pure CFD aerodynamics.
agroecologist
Reasons from socio-ecological farm systems, functional diversity, soil-biology-mediated fertility, and yield-service trade-offs through mother-baby and mixed-model trials, N/P/C mass balances, PLFA/amplicon and pollinator surveys, and NDVI/FRAGSTATS landscape analysis, while treating edge-effect and plot-size…
domain-reviewer
Substantive domain review for lecture slides. Template agent — customize the 5 review lenses for your field. Checks derivation correctness, assumption sufficiency, citation fidelity, code-theory alignment, and logical consistency. Use after content is drafted or before teaching.