running-r

running-r is a skill for Claude Code from yale-som-hpc/claude-code-marketplace. It costs 68 tokens per session (2,111 once invoked), scanned A, original, Unlicense.

Guidance for running R, a statistics and data-analysis language, on Yale SOM's shared computing cluster. It covers versioned software modules, renv project libraries, batch scripts, and thread settings.

In plain words
What is it for?
Setting up R packages, restoring an renv.lock file, writing R Slurm jobs, controlling BLAS or OpenMP threads, and running R scripts in batch mode.
Why use it?
It prevents jobs from relying on missing packages or changing software versions, and makes the same project reproducible across cluster nodes.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the hpc plugin — 23 skills, 3 commands shipped together

Good fit Setting up R packages, restoring an renv.lock file, writing R Slurm jobs, controlling BLAS or OpenMP threads, and running R scripts in batch mode.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/yale-som-hpc/claude-code-marketplace/running-r
Install

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.

Any agent
npx skills add yale-som-hpc/claude-code-marketplace --skill running-r
Clone the repo
git clone --depth 1 https://github.com/yale-som-hpc/claude-code-marketplace

Made for: Claude Code.

Or install hpc, the plugin that ships this one along with the rest of its 23 skills, 3 commands.

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.

agentmods badge for running-r

README.md
[![agentmods](https://agentmods.dev/badge/skills/yale-som-hpc/claude-code-marketplace/running-r/github.svg)](https://agentmods.dev/skills/yale-som-hpc/claude-code-marketplace/running-r)
Your own site
<a href="https://agentmods.dev/skills/yale-som-hpc/claude-code-marketplace/running-r"><img src="https://agentmods.dev/badge/skills/yale-som-hpc/claude-code-marketplace/running-r/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.

agentmods 80×15 button for running-r

Your own site · 80×15
<a href="https://agentmods.dev/skills/yale-som-hpc/claude-code-marketplace/running-r"><img src="https://agentmods.dev/badge/skills/yale-som-hpc/claude-code-marketplace/running-r.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 68 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,111 The whole file, excluding the scripts and references it only reads on demand.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00068 $0.02111
Opus 5 $0.00034 $0.01056
Sonnet 5 $0.00014 $0.00422
Haiku 4.5 $0.00007 $0.00211

Measured 11d ago against content hash 9694639ebd36, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

running-r 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.

plugins/hpc/skills/running-r/SKILL.md · 200 lines

How it starts

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

Running R

Rule: load R explicitly, restore packages deliberately, and never let package installs happen inside large job arrays.

Tooling defaults

Slightly opinionated picks for new R projects on the cluster:

  • Cluster R module for the R executable. Load it explicitly in every job script, and pin the version for reproducibility — pick one from module spider r and module load r/<version>, rather than bare module load r, which follows the moving default.
  • The base R module ships essentially no add-on packages — not even renv. optparse, data.table, arrow, tidyverse, here, fixest, etc. are all absent until you install them. Your very first setup step is bootstrapping a project library (see "Use renv carefully"); a job that library(optparse) without that step will fail with there is no package called 'optparse'.
  • renv for project libraries. renv.lock is the R analogue of uv.lock — it is what makes runs reproducible from login node to compute node.
  • pak as the installer behind renv for fast parallel installs.
  • lintr + styler for static checks and formatting; testthat for tests. Install once at project setup.
  • optparse for CLI scripts (one-file batch entry points like the pattern below).
  • Native pipe |> unless you specifically need magrittr's %>% placeholders.

Style defaults

For the audience that is new to R — these are not stylistic preferences, they are the conventions that will make your code readable to anyone who comes after you (including future-you):

  • snake_case for variables and functions; reserve CamelCase for S4/R6 classes.
  • <- for assignment, not =. (Reserve = for named function arguments.)
  • All library() calls at the top of the script.
  • File paths via here::here() or explicit project paths; do not hardcode laptop paths.
  • Always set set.seed() for stochastic work.
  • Always use named arguments where the meaning is not obvious: mean(x, na.rm = TRUE), not mean(x, T).
  • Smoke test on a small slice of real data before submitting a full cluster job. This is genuinely the fastest debugging loop you have.

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

  1. 11d ago First seen · 200 lines · 68 tokens per session scan A 9694639ebd36

Subscribe to this mod's changes

running-r is a skill published in the GitHub repository yale-som-hpc/claude-code-marketplace (5 stars, last pushed 2mo ago), licensed Unlicense. It adds 68 tokens to every session and 2,111 once invoked, about $0.0003 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.

Related

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…

anthropics/knowledge-work-plugins · 123 tokens

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…

K-Dense-AI/scientific-agent-skills · 83 tokens

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.

K-Dense-AI/scientific-agent-skills · 42 tokens

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.

K-Dense-AI/scientific-agent-skills · 68 tokens

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.

davila7/claude-code-templates · 43 tokens

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…

maziyarpanahi/openmed · 205 tokens