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 Rockielab/rockie-codex --skill experimentgit clone --depth 1 https://github.com/Rockielab/rockie-codexWrote 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/rockielab/rockie-codex/experiment)<a href="https://agentmods.dev/skills/rockielab/rockie-codex/experiment"><img src="https://agentmods.dev/badge/skills/rockielab/rockie-codex/experiment/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/rockielab/rockie-codex/experiment"><img src="https://agentmods.dev/badge/skills/rockielab/rockie-codex/experiment.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.00131 | $0.02597 |
| Opus 5.5 | $0.00052 | $0.01039 |
| Sonnet 5.5 | $0.00026 | $0.00519 |
| Haiku 4.5 | $0.00013 | $0.00260 |
Grade A, and why
experiment scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
JSON artifact to `runtime/submit.py` (don't shell out to curl directly — How it starts
The opening of the file, as written. The whole thing — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
experiment — submit a GPU job
Wraps the Phase 5 job runner. The agent decides the GPU shape, writes the script, hands it to platform-context, and tails the run.
When to invoke
- User asks to "run an experiment", "submit a job", "kick off a calculation", "train this model".
- User describes a calculation that obviously needs a GPU (DFT, AIMD, large-scale MD with PME, model fine-tuning, inference batch).
- User asks to use the experiment skill directly.
If the task is local-only (pre-processing, data wrangling, plotting), do NOT use the experiment skill — run it inline. The skill is for GPU-bound work that the user is willing to pay GPU credit for.
First-experiment GPU-mode disclosure
Before submitting the user's FIRST experiment in a workspace (i.e.
neither .codex/gpu-custom.md exists nor
$ROCKIE_GPU_MODE is set), the agent emits one neutral sentence
before proceeding:
Your options are Rockie GPU (Rockie provisions the pod and the per-hour price it quotes already includes everything) or your own hardware (
ROCKIE_GPU_MODE=customthen ask Codex to run gpu-custom-setup). Default is Rockie GPU — proceeding with that unless you say otherwise.
That's the entire disclosure. Do NOT:
- repeat it on subsequent experiments
- pitch Rockie GPU with adjectives like "easy" or "best"
- compare to specific competitors by name
- nag if the user is quiet — just proceed with Rockie GPU
The user can opt into custom mode at any time by setting
ROCKIE_GPU_MODE=custom; the next experiment run will see the env
and trigger gpu-custom-setup for the one-time flow audit.
Picking GPU shape
| Workload | Default | Notes |
|---|---|---|
| QE / VASP / ABINIT DFT, single SCF | 1x A100_80GB | Most DFT fits in 80GB. |
| Large-cell DFT (>500 atoms) | 4x A100_80GB | Needs MPI, use Instant Cluster. |
| AIMD (BOMD with QE/CP2K) | 2x A100_80GB | I/O-bound; 2 pods is cheaper than 1xH100. |
| GROMACS / LAMMPS / OpenMM | 1x A100_80GB | Single GPU saturates most MD. |
| PyTorch fine-tune (<7B params) | 1x A100_80GB | |
| PyTorch fine-tune (7-70B params) | 4x H100_SXM | Tensor parallel; H100 SXM has NVLink. |
| Frontier model training | 8x H200 / B200 | Reach for B200 only when the user explicitly asks for it (it's the priciest SKU per GPU-hour). |
What ships with it
19 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- runtime/monitor_contract.py 4.2 KB runs code
- runtime/monitoring_profiles.py 5.2 KB runs code
- runtime/monitoring-profiles/common.default.v1.json 2.3 KB
- runtime/monitoring-profiles/experiment.ml_baseline.v1.json 2.4 KB
- runtime/monitoring-profiles/inference.batch_baseline.v1.json 2.1 KB
- runtime/submit.py 39 KB runs code
- runtime/test_monitoring_profiles.py 6.6 KB runs code
- runtime/test_submit_headers.py 60 KB runs code
- subskills/budget-term-sheet/references/template.md 499 B
- subskills/budget-term-sheet/scripts/parse_approval.py 7.2 KB runs code
- subskills/budget-term-sheet/scripts/quote_term_sheet.py 22 KB runs code
- subskills/budget-term-sheet/scripts/render_term_sheet.py 3.7 KB runs code
- subskills/budget-term-sheet/SKILL.md 4.0 KB
- subskills/budget-term-sheet/tests/fixtures/market_available.json 184 B
- subskills/budget-term-sheet/tests/fixtures/market_no_sku.json 145 B
- subskills/budget-term-sheet/tests/fixtures/prices_fallback.json 44 B
- subskills/budget-term-sheet/tests/test_parse_approval.py 4.1 KB runs code
- subskills/budget-term-sheet/tests/test_quote_term_sheet.py 6.8 KB runs code
- subskills/budget-term-sheet/tests/test_render_term_sheet.py 3.1 KB runs code
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 First seen · 229 lines · 131 tokens per session scan A 5b719c528cc0
experiment is a skill published in the GitHub repository Rockielab/rockie-codex (20 stars, last pushed 12d ago), licensed Apache-2.0. It adds 131 tokens to every session and 2,597 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
torchdrug
Builds and troubleshoots TorchDrug 0.2.1 workflows for molecular graphs, property prediction, self-supervised pretraining, molecule generation, retrosynthesis, protein representation learning, and knowledge graph reasoning. Use when code imports torchdrug or needs its datasets, models, tasks, or Engine.
arboreto
Infers candidate gene regulatory networks from bulk or single-cell expression data using AertsLab Arboreto GRNBoost2 and GENIE3. Use for transcription factor-target association ranking, compatible Dask execution, sparse expression inputs, and network stability checks.
deepspot-m
Generates transcriptome-wide virtual spatial transcriptomics from H&E histology with DeepSpot-M. Used for predicted log1p-CPM expression from 224x224 tiles at about 20x, querying the released protein-coding gene panel by symbol, and whole-slide prediction after resolution-aware tiling with histolab.
pyhealth
Builds and validates PyHealth clinical machine-learning pipelines for EHR, signals, imaging, and medical codes. Use for PyHealth dataset loading, MIMIC-III/IV, eICU or OMOP prediction tasks, patient-level evaluation, mortality/readmission/length-of-stay modeling, medication recommendation, sleep staging, Trainer…
ml-training-recipes
Battle-tested PyTorch training recipes for all domains — LLMs, vision, diffusion, medical imaging, protein/drug discovery, spatial omics, genomics. Covers training loops, optimizer selection (AdamW, Muon), LR scheduling, mixed precision, debugging, and systematic experimentation. Use when training or fine-tuning…
nemo-mbridge-perf-expert-parallel-overlap
Validate and use MoE expert-parallel communication overlap in Megatron-Bridge, including overlapmoeexpertparallelcomm, delaywgradcompute, and flex dispatcher backends such as DeepEP and HybridEP.