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 ualberta-rcg/drac-agent-skills --skill alliance-slurmgit clone --depth 1 https://github.com/ualberta-rcg/drac-agent-skillsWrote 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/ualberta-rcg/drac-agent-skills/alliance-slurm)<a href="https://agentmods.dev/skills/ualberta-rcg/drac-agent-skills/alliance-slurm"><img src="https://agentmods.dev/badge/skills/ualberta-rcg/drac-agent-skills/alliance-slurm/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/ualberta-rcg/drac-agent-skills/alliance-slurm"><img src="https://agentmods.dev/badge/skills/ualberta-rcg/drac-agent-skills/alliance-slurm.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.00078 | $0.02770 |
| Opus 5 | $0.00039 | $0.01385 |
| Sonnet 5 | $0.00016 | $0.00554 |
| Haiku 4.5 | $0.00008 | $0.00277 |
Grade A, and why
alliance-slurm 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 11d 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 — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Alliance (DRAC) Slurm
Alliance clusters run Slurm with a custom Lua submission layer that auto-routes jobs and a prolog that injects environment variables. Hardware varies by cluster — always discover before assuming. Auth is managed via CCDB; software modules come from CVMFS.
For cluster policies, storage quotas, and account questions, check alliance-docs first.
Discovery — never hardcode, always list
Run these first on any new cluster. Never guess account names, GPU types, partition names, or QOS values.
# Partitions and time limits
sinfo -s # TIMELIMIT column is authoritative
# GPU GRES inventory (look for composite entries, e.g. gpu:l40s:4,shard:l40s:16)
sinfo -h -o "%G" --Node | sort -u
sinfo -h -o "%N %G %f" --Node | sort -u # adds features (softmig, etc.)
# Full GRES detail on a specific node
scontrol show node <node> | grep -E 'Gres=|CfgTRES='
# Accounts available to you
sacctmgr show assoc user=$USER format=Account,DefaultAccount,QOS -p
# QOS limits (MaxWall / MaxTRES are often blank; prefer sinfo -s for walltime)
sacctmgr show qos format=Name,MaxWall,MaxTRES,Priority -p
# Fairshare / software
sshare -U
module avail && module spider <name>
Always run GPU discovery before writing --gres flags. GPU type names (v100l,
a100, l40s, h100, …) differ by cluster and node.
Partitions — usually omit
A Lua plugin auto-routes jobs based on --time. Omit --partition unless you have
a concrete reason (e.g. forcing CPU-only). Setting it with a mismatched --time
causes instant rejection.
- Time tiers go up to a 7-day maximum; requests over 7 days are rejected.
srun/sallocalways route to the interactive partition. Check actual limits withsinfo -s— GPU interactive is often longer than CPU interactive (e.g. 8 h vs 3 h).
Key flags
| Flag | Notes |
|---|---|
--account=<acct> |
Required when you have multiple accounts or must charge a specific project. Check with sacctmgr show assoc user=$USER; omit only if your default account is correct. |
--time=HH:MM:SS |
Default is 60 min. Drives partition routing. Always set. |
--mem=... |
Default is very low, cgroup-enforced. Always set. |
--gres=gpu:<type>:N |
Use exact type string from sinfo discovery. Bare gpu:N is unreliable and is rejected on general-purpose clusters (fir, nibi, rorqual, and similar). Always use the full type string. |
--cpus-per-task=N |
Default is 1. |
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.
- 11d ago First seen · 258 lines · 78 tokens per session scan A 85e56374efc8
alliance-slurm is a skill published in the GitHub repository ualberta-rcg/drac-agent-skills (2 stars, last pushed 8d ago), licensed MIT. It adds 78 tokens to every session and 2,770 once invoked, about $0.0004 per session on Opus 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-31.
Other skills, from other repositories
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
exploratory-data-analysis
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…
matlab
Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.
phylogenetics
Build and analyze phylogenetic trees using MAFFT (multiple alignment), IQ-TREE 2 (maximum likelihood), and FastTree (fast NJ/ML). Visualize with ETE3 or FigTree. For evolutionary analysis, microbial genomics, viral phylodynamics, protein family analysis, and molecular clock studies.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…