Borrowing it
Nothing to install: this file belongs to AMDResearch/ai4science-studio. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/AMDResearch/ai4science-studio/main/.claude/commands/run-matey.mdgit 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/commands/amdresearch/ai4science-studio/run-matey)<a href="https://agentmods.dev/commands/amdresearch/ai4science-studio/run-matey"><img src="https://agentmods.dev/badge/commands/amdresearch/ai4science-studio/run-matey/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/commands/amdresearch/ai4science-studio/run-matey"><img src="https://agentmods.dev/badge/commands/amdresearch/ai4science-studio/run-matey.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.00730 |
| Opus 5.5 | $0.00000 | $0.00292 |
| Sonnet 5.5 | $0.00000 | $0.00146 |
| Haiku 4.5 | $0.00000 | $0.00073 |
Grade A, and why
run-matey 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.
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run MATEY spatiotemporal modeling on an AMD cluster
Guide the user through training or inference with MATEY on AMD GPUs.
Step 0 — Cluster config check
Check if .cluster-config.yaml (repo root) or ~/.config/ai4science-studio/cluster.yaml exists. If neither exists, run the /init-cluster flow first. If a config exists, read it and pre-fill container runtime and SLURM partition/account from saved values.
Step 1 — Questionnaire
Q0. Task
- Training — Train a MATEY model from scratch
- Inference — Autoregressive rollout from a trained checkpoint
Q1. Container runtime
- Apptainer (recommended for HPC — use
build_sif.shto create SIF + overlay) - Docker (simpler setup)
Q2. (Training) Dataset Do you have training data in HDF5 format? The JHTDB turbulence demo data is the default starting point.
Q3. (Training) Multi-GPU Single GPU or multi-GPU DDP? If multi-GPU, how many?
Q4. (Inference) Checkpoint path
Full path to your trained .pt checkpoint?
Q5. (Inference) Input file Path to HDF5 initial condition file?
Q6. (SLURM) Partition and account How should I determine your SLURM partition and account/project?
- Provide manually — type your partition and account names
- Auto-discover — I will query SLURM to find available partitions and accounts on this cluster
Step 2 — Setup
Auto-discovery procedures
Run these when the user chose Auto-discover for any question. Present the results and let the user confirm or override.
SLURM partition and account (Q6):
sinfo -h -o "%P %G" | grep -i gpu
sacctmgr show associations where user=$USER format=account%30,partition%30 -n
Present the available GPU partitions and the user's associated accounts. If multiple exist, ask the user to pick.
After auto-discovery, always confirm the found values with the user before proceeding.
Docker
cd physics_simulation/models/MATEY/examples
./docker_run.sh train # or: ./docker_run.sh inference
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 · 94 lines · 0 tokens per session scan A 70b8722940bf
run-matey is a command published in the GitHub repository AMDResearch/ai4science-studio (4 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 730 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.
run-matey compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| run-mateyAMDResearch/ai4science-studio | Command | 4 | yesterday | MIT | A | 0 | Claude Code |
| by:campaign-auto001TMF/blatant-why | Command | 119 | 22d ago | MIT | A | 19 | Claude Code |
| by:load001TMF/blatant-why | Command | 119 | 22d ago | MIT | A | 13 | Claude Code |
| by:approve-lab001TMF/blatant-why | Command | 119 | 22d ago | MIT | A | 21 | Claude Code |
| ml-projectmxslr/mlcraft | Command | 8 | 4mo ago | MIT | A | 52 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 27 | Claude Code |