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 --skill analyze-convergencegit 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/analyze-convergence)<a href="https://agentmods.dev/skills/equinor/neqsim/analyze-convergence"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/analyze-convergence/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/analyze-convergence"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/analyze-convergence.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.00016 | $0.01936 |
| Opus 5.5 | $0.00006 | $0.00774 |
| Sonnet 5.5 | $0.00003 | $0.00387 |
| Haiku 4.5 | $0.00002 | $0.00194 |
Grade A, and why
analyze-convergence 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.
This is a copy
98% identical to analyze_convergence — 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.
How it starts
The opening of the file, as written. The whole thing — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Analyze Convergence
Purpose
Interpret flash algorithm convergence metrics, identify patterns, and produce publication-quality analysis for the Results section.
When to Use
- After running benchmark experiments
- When comparing baseline vs candidate algorithms
- When investigating failure cases
Analysis Procedure
Step 1: Load and Parse Results
import json
import pandas as pd
def load_results(results_dir, algorithm_name):
"""Load JSONL results into DataFrame."""
records = []
with open(f"{results_dir}/raw/{algorithm_name}_results.jsonl") as f:
for line in f:
records.append(json.loads(line))
return pd.DataFrame(records)
Step 2: Convergence Rate by Family
def convergence_by_family(df):
"""Calculate convergence rate per fluid family."""
return df.groupby("family").agg(
total=("converged", "count"),
converged=("converged", "sum"),
rate_pct=("converged", lambda x: round(100 * x.mean(), 2)),
median_time_ms=("cpu_time_ms", "median")
).reset_index()
Step 3: Convergence Maps
Generate 2D convergence maps in (T, P) space:
import matplotlib.pyplot as plt
import numpy as np
def plot_convergence_map(df, family_name, algorithm_name, save_path):
"""Plot convergence success/failure in TP space."""
fam = df[df["family"] == family_name]
fig, ax = plt.subplots(figsize=(8, 6))
conv = fam[fam["converged"] == True]
fail = fam[fam["converged"] == False]
ax.scatter(conv["T_K"] - 273.15, conv["P_bara"],
c="green", alpha=0.3, s=10, label="Converged")
ax.scatter(fail["T_K"] - 273.15, fail["P_bara"],
c="red", alpha=0.8, s=20, marker="x", label="Failed")
ax.set_xlabel("Temperature (°C)")
ax.set_ylabel("Pressure (bara)")
ax.set_title(f"Convergence Map — {family_name} — {algorithm_name}")
ax.legend()
ax.grid(True, alpha=0.3)
ax.set_yscale("log")
plt.tight_layout()
plt.savefig(save_path, dpi=300, bbox_inches="tight")
plt.close()
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.
- 27d ago First seen · 234 lines · 16 tokens per session scan A 624dd0b7580b
analyze-convergence 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,936 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 98% identical to analyze_convergence, differing in 2 lines, and is treated as a copy.
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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.
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…
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…