Project rules for running complex scientific simulations with multiple agents, including research, setup, review, execution, and result checking.

Use them to research simulation parameters, create solver inputs, inspect meshes and boundary conditions, run simulations, and validate outputs.

They organize simulation work and require important inputs, units, settings, and results to be checked independently.

How Hereon-InstituteMS/OASiS configures Cursor

Reuse

Borrowing it

Nothing to install: this file belongs to Hereon-InstituteMS/OASiS. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/Hereon-InstituteMS/OASiS/main/.cursorrules

Clone the repo

git clone --depth 1 https://github.com/Hereon-InstituteMS/OASiS

Made for: Cursor.

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.

README.md

[![agentmods](https://agentmods.dev/badge/rules/hereon-institutems/oasis/cursorrules/github.svg)](https://agentmods.dev/rules/hereon-institutems/oasis/cursorrules)

Your own site

<a href="https://agentmods.dev/rules/hereon-institutems/oasis/cursorrules"><img src="https://agentmods.dev/badge/rules/hereon-institutems/oasis/cursorrules/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.

Your own site · 80×15

<a href="https://agentmods.dev/rules/hereon-institutems/oasis/cursorrules"><img src="https://agentmods.dev/badge/rules/hereon-institutems/oasis/cursorrules.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 786 This file is loaded in full into every session.

When invoked 786 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found 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.

Model	Per session	Once invoked
Fable 5.1	$0.00786	$0.00786
Opus 5.5	$0.00314	$0.00314
Sonnet 5.5	$0.00157	$0.00157
Haiku 4.5	$0.00079	$0.00079

Measured 2mo ago against content hash 6e920fd0b856, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

cursorrules 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 2mo 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.

.cursorrules · 52 lines

How it starts

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

OASiS — Project Instructions

How to Handle Complex Simulation Tasks

For any non-trivial simulation task, break the work into sub-agents:

Research agent: Search online for the specific problem — find literature values, validated setups, correct parameters. Report findings.
Setup agent: Using the research findings, build the input files. Use get_example_inputs() to study real test files from the solver's test suite. Use run_with_generator() for simulations that need programmatic mesh/particle generation.
Critic agent: Independently review the setup. Check every parameter against what the research agent found. Verify units, discretization, boundary conditions, material properties. Search online to validate. If the simulation fails after multiple attempts with the chosen solver, consider whether an alternative solver might be more suitable — prepare_simulation shows what alternatives exist. Report any issues.
Execution agent: Fix any issues the critic found, then run the simulation.
Results critic agent: After the simulation completes, independently verify the results. Use visualize(action='validate') to check for NaN, constant fields, suspiciously large values. Check that field magnitudes are physically reasonable for the problem. Compare against known analytical solutions or literature values where possible.
Coupling agent (if multi-solver): Transfer fields between solvers, set up the coupling, run the second solver, produce combined output.

Developer Mode: Extending Solvers

When you hit a solver limitation — a missing material model, element type, boundary condition, or physics module — don't just accept it. You have full source access via developer(action='architecture', solver) and the <SOLVER>_ROOT environment variables. Consider:

Diagnose: Read the solver source to understand why the capability is missing
Assess: Is it a small addition (new material, new BC) or a major feature? Report this to the user.
Propose: Tell the user "I could implement X in the solver source to fix this — should I proceed?"
Implement (if authorized): Modify source files, rebuild, re-run with the fix

Read the full file on GitHub · 52 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.

2mo ago First seen · 52 lines · 786 tokens per session scan A 6e920fd0b856

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository Hereon-InstituteMS/OASiS (23 stars, last pushed 2mo ago), licensed MIT. It adds 786 tokens to every session, about $0.0031 per session on Opus 5.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.

Building agents FEniCS Planning computational-mechanics dealii finite-element-method llm-agent mcp-server

cursorrules next to 6 cursor rules from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
cursorrulesHereon-InstituteMS/OASiS	Cursor rule	23	2mo ago	MIT	A	786	Cursor
about-codebaselineai-intelligence/lineai-mcp-server	Cursor rule	37	11d ago	MPL-2.0	A	13	Cursor
toc-readmekontent-ai/mcp-server	Cursor rule	10	2d ago	MIT	A	0	Cursor
runwhen-infrastructurerunwhen-contrib/runwhen-platform-mcp	Cursor rule	1	5d ago	Apache-2.0	A	0	Cursor
php-client-implementationdalehurley/php-mcp-sdk	Cursor rule	27	11mo ago	MIT	A	8	Cursor
cursor_rulesgiantswarm/mcp-prometheus	Cursor rule	11	yesterday	Apache-2.0	A	374	Cursor
validate-design-earlyRethunk-AI/clodbridge	Cursor rule	0	4mo ago	MIT	A	227	Cursor

OASiS: Cursor rule for Cursor