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 regen-coordination/org-os-template --skill runpod-computegit clone --depth 1 https://github.com/regen-coordination/org-os-templateWrote 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/regen-coordination/org-os-template/runpod-compute)<a href="https://agentmods.dev/skills/regen-coordination/org-os-template/runpod-compute"><img src="https://agentmods.dev/badge/skills/regen-coordination/org-os-template/runpod-compute/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/regen-coordination/org-os-template/runpod-compute"><img src="https://agentmods.dev/badge/skills/regen-coordination/org-os-template/runpod-compute.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.00038 | $0.00435 |
| Opus 5 | $0.00019 | $0.00217 |
| Sonnet 5 | $0.00008 | $0.00087 |
| Haiku 4.5 | $0.00004 | $0.00044 |
Grade C, and why
runpod-compute scanned grade C 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 8d 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.
Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
ssh root@<IP> -p <PORT> -i ~/.ssh/id_ed25519 What it actually says
RunPod Compute
Use runpodctl CLI for persistent GPU pods with SSH access.
Setup
brew install runpod/runpodctl/runpodctl # macOS
runpodctl config --apiKey=YOUR_KEY
Commands
| Command | Description |
|---|---|
runpodctl create pod --gpuType "NVIDIA A100 80GB PCIe" --imageName "runpod/pytorch:2.4.0-py3.11-cuda12.4.1-devel-ubuntu22.04" --name experiment |
Create a pod |
runpodctl get pod |
List all pods |
runpodctl stop pod <id> |
Stop (preserves volume) |
runpodctl start pod <id> |
Resume a stopped pod |
runpodctl remove pod <id> |
Terminate and delete |
runpodctl gpu list |
List available GPU types and prices |
runpodctl send <file> |
Transfer files to/from pods |
runpodctl receive <code> |
Receive transferred files |
SSH access
ssh root@<IP> -p <PORT> -i ~/.ssh/id_ed25519
Get connection details from runpodctl get pod <id>. Pods must expose port 22/tcp.
GPU types
NVIDIA GeForce RTX 4090, NVIDIA RTX A6000, NVIDIA A40, NVIDIA A100 80GB PCIe, NVIDIA H100 80GB HBM3
When to use
- Long-running experiments needing persistent state
- Large dataset processing
- Multi-step work with SSH access between iterations
- Always stop or remove pods after experiments
- Check availability:
command -v runpodctl
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.
- 8d ago First seen · 49 lines · 38 tokens per session scan C a7c794f63419
runpod-compute is a skill published in the GitHub repository regen-coordination/org-os-template (5 stars, last pushed 2d ago), licensed MIT. It adds 38 tokens to every session and 435 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
latchbio-integration
Build, register, debug, and operate bioinformatics workflows on Latch using the Python SDK, CLI, Latch Data and Registry, Nextflow, Snakemake, programmatic execution, and Latch MCP. Use when authoring or deploying Latch workflows, configuring resources or interfaces, moving data, integrating Registry, or launching and…
remote-compute-ssh
Evaluate and use SSH Remote Compute before choosing where to run GPU, high-memory, parallel, batch, model-inference, bioinformatics, or other long-running scientific work; supports short remote commands and asynchronous jobs with automatic harvest and analysis.
modal-compute
Run explicitly chosen research benchmark or replication jobs on Modal's serverless infrastructure. Use when a Feynman research workflow needs burst remote GPU compute and the Modal CLI is available.
dnanexus-integration
DNAnexus cloud genomics platform. Build apps/applets, manage data (upload/download), dxpy Python SDK, run workflows, FASTQ/BAM/VCF, for genomics pipeline development and execution.
latchbio-integration
Latch platform for bioinformatics workflows. Build pipelines with Latch SDK, @workflow/@task decorators, deploy serverless workflows, LatchFile/LatchDir, Nextflow/Snakemake integration.
modal-serverless-gpu
Run approved CPU or GPU work through OpenScience computejob on the user's configured Modal account. Use for isolated scientific scripts, dependency provisioning, durable outputs, logs, status, cancellation, and recovery. Never invoke the Modal SDK or CLI directly.