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/AMDResearch/ai4science-studioWrote 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/rules/amdresearch/ai4science-studio/sbatch-scripts)<a href="https://agentmods.dev/rules/amdresearch/ai4science-studio/sbatch-scripts"><img src="https://agentmods.dev/badge/rules/amdresearch/ai4science-studio/sbatch-scripts/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/rules/amdresearch/ai4science-studio/sbatch-scripts"><img src="https://agentmods.dev/badge/rules/amdresearch/ai4science-studio/sbatch-scripts.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.00000 | $0.00844 |
| Opus 5.5 | $0.00000 | $0.00338 |
| Sonnet 5.5 | $0.00000 | $0.00169 |
| Haiku 4.5 | $0.00000 | $0.00084 |
Grade A, and why
sbatch-scripts 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 1mo 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SLURM sbatch script conventions
When creating or editing sbatch_*.sh under any model's examples/ directory:
Required patterns
-
SCRIPT_DIR resolution — Use
scontrolto recover the original script path (SLURM copies scripts to/var/spool/slurmd/):if [[ -n "${SLURM_JOB_ID:-}" ]]; then SCRIPT_DIR=$(cd "$(dirname "$(scontrol show job "$SLURM_JOB_ID" | grep -oP 'Command=\K\S+')")" && pwd) else SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)" fi -
Use
--rocmfor AMD GPU passthrough — Never use--nv(that is for NVIDIA):apptainer exec --rocm ... -
Naming convention — Scripts are named
sbatch_<task>_amd.sh, not_mi300x.shor_mi250x.sh. The samerocm7.2.ximage covers MI250X (gfx90a), MI300X (gfx942), and MI350X (gfx950). -
Placeholder partition/account — Use
YOUR_PARTITION_HEREandYOUR_ACCOUNT_HEREin#SBATCHdirectives so users (or agents) know to replace them:#SBATCH --partition=YOUR_PARTITION_HERE #SBATCH --account=YOUR_ACCOUNT_HERE -
No site-specific paths — including in defaults — Never hardcode user- or cluster-specific paths anywhere in the script, including as default values for env vars. This is the most common mistake: satisfying "paths come from env vars" while still baking a site-specific path into the default.
Wrong:
HG_SIF="${HG_SIF:-/shared/username/models/HydraGNN/images/rocm_pytorch.sif}"Right — use
AI4S_SHARED_DIR(set by the user for their site) or leave the default empty and fail with a clear message:# Option A: relative to a user-set base dir HG_BASE="${AI4S_SHARED_DIR:-}/models/HydraGNN" HG_SIF="${HG_SIF:-${HG_BASE}/images/rocm_pytorch.sif}" # Option B: no default — require the user to set it : "${HG_SIF:?Set HG_SIF to your Apptainer SIF path}"Site-specific values (partition, account, shared dir, scratch paths) belong in the gitignored
.cluster-config.yaml/~/.config/ai4science-studio/cluster.yaml, not in committed scripts.make checkenforces this viaai4s_validate.site_leaks.
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.
- 1mo ago Changed 7c432951eeb3
- 1mo ago First seen · 66 lines · 0 tokens per session scan A a0e580f8a3b2
sbatch-scripts is a cursor rule published in the GitHub repository AMDResearch/ai4science-studio (4 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 844 tokens. 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-31.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).