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 paperlab-derivation-symbolic-checkinggit 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/paperlab-derivation-symbolic-checking)<a href="https://agentmods.dev/skills/equinor/neqsim/paperlab-derivation-symbolic-checking"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/paperlab-derivation-symbolic-checking/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/paperlab-derivation-symbolic-checking"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/paperlab-derivation-symbolic-checking.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.00036 | $0.00346 |
| Opus 5.5 | $0.00014 | $0.00138 |
| Sonnet 5.5 | $0.00007 | $0.00069 |
| Haiku 4.5 | $0.00004 | $0.00035 |
Grade A, and why
paperlab-derivation-symbolic-checking 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
100% identical to paperlab_derivation_symbolic_checking — 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.
What it actually says
PaperLab Derivation Symbolic Checking
When to Use
USE WHEN: a paper or book includes a new method, equation derivation, algorithm description, Jacobian, residual formulation, or thermodynamic identity.
Audit Dimensions
| Dimension | Questions |
|---|---|
| Assumptions | Are phase, EOS, ideality, and differentiability assumptions explicit? |
| Units | Are both sides dimensionally consistent? |
| Symbols | Are symbols defined once and reused consistently? |
| Limiting cases | Does the equation reduce correctly for simple or ideal cases? |
| Code linkage | Is there a Java method, notebook, or test implementing the equation? |
Output Schema
{
"equations": [
{
"label": "residual_jacobian",
"status": "needs_fix",
"issues": ["symbol J reused for flux and Jacobian"],
"limiting_cases_checked": ["ideal gas", "zero association"],
"implementation_link": "neqsim.package.Class#method"
}
]
}
Pass Criteria
- Each derivation states assumptions.
- Units and symbols are consistent.
- At least one limiting case or reference comparison is described.
- Implementation or test linkage exists for computational methods.
Safety Rules
- Do not present dimensional consistency as mathematical proof.
- If symbolic algebra cannot be run, state that the review is manual.
- Keep corrections minimal and tied to the manuscript text.
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 · 52 lines · 36 tokens per session scan A 8ee75ffd22ae
paperlab-derivation-symbolic-checking is a skill published in the GitHub repository equinor/neqsim (156 stars, last pushed today), licensed Apache-2.0. It adds 36 tokens to every session and 346 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to paperlab_derivation_symbolic_checking, 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…