Open Science is a local-first, model-agnostic workbench for reproducible scientific research. Scientists use its AI agents, Python and R execution, data connectors, and traceable outputs for tasks such as literature review, analysis, simulation, and visualization across macOS, Windows, and Linux.
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 aipoch/open-science --skill compute-env-setupgit clone --depth 1 https://github.com/aipoch/open-scienceWrote 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/aipoch/open-science/compute-env-setup)<a href="https://agentmods.dev/skills/aipoch/open-science/compute-env-setup"><img src="https://agentmods.dev/badge/skills/aipoch/open-science/compute-env-setup/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/aipoch/open-science/compute-env-setup"><img src="https://agentmods.dev/badge/skills/aipoch/open-science/compute-env-setup.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.00060 | $0.02075 |
| Opus 5 | $0.00030 | $0.01038 |
| Sonnet 5 | $0.00012 | $0.00415 |
| Haiku 4.5 | $0.00006 | $0.00208 |
Grade A, and why
compute-env-setup 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 yesterday.
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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Compute environment setup
Prepare one reproducible environment definition and instructions for one small user-managed host
activation file. Open Science resolves submitJob(..., { environment: '<name>' }) by sourcing
~/.openscience/environments/<name>.sh before the workload. The file contains activation only; it
does not install packages when a job starts.
The environment, package caches, images, and activation file are user-managed durable resources,
not Open Science-owned components. This Skill may inspect them and prepare exact setup/removal
commands, but must not execute commands that create, replace, or remove those resources. The user
or host administrator runs those commands outside Open Science and owns their lifecycle. Do not
interpret the ~/.openscience path as app ownership.
Use host.compute only in repl_execute JavaScript. Python and R data kernels do not expose it.
Start from the Session catalog and do not guess a provider id:
const hosts = await host.compute.listHosts()
const selected = hosts.filter((candidate) => candidate.role === 'selected')
const candidates = selected.length > 0 ? selected : hosts
Choose the requested host, or a suitable candidate when the user left the target open. Read its knowledge and probe snapshot before changing it:
const providerId = candidates[0].provider_id
const executionMode = candidates[0].execution_mode
const details = await host.compute.details(providerId, { mode: 'read' })
const compute = host.compute.create(providerId)
If no eligible host exists, or the selected host is unsuitable, explain the concrete blocker. Do not install locally as a substitute for a requested remote environment.
Define the environment
Keep the reproducible source in the user's project: an environment.yml, requirements or lock
file, container definition, or a short setup script appropriate to the stack. When installation
must run on a compute node, include exact user- or administrator-run staging and scheduler commands
in the plan; do not submit that installation through Open Science. Do not store project package
lists or secrets in the host knowledge document.
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.
- yesterday First seen · 188 lines · 60 tokens per session scan A b685e78087c5
compute-env-setup is a skill published in the GitHub repository aipoch/open-science (4,137 stars, last pushed today), licensed Apache-2.0. It adds 60 tokens to every session and 2,075 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-09-07.
Other skills, from other repositories
eng-runbook
A one-page engineering runbook: a practical guide for operating a software service. It includes alerts, dashboards, procedures, on-call information, and an incident checklist.
render-html
A command-line tool for managing GPU jobs on the Qizhi computing platform, a service for running machine-learning workloads on shared graphics processors.
vast-gpu
Rent, manage, and destroy GPU instances on vast.ai. Use when user says "rent gpu", "vast.ai", "rent a server", "cloud gpu", or needs on-demand GPU without owning hardware.
serverless-modal
Run GPU workloads on Modal — training, fine-tuning, inference, batch processing. Zero-config serverless: no SSH, no Docker, auto scale-to-zero. Use when user says "modal run", "modal training", "modal inference", "deploy to modal", "need a GPU", "run on modal", "serverless GPU", or needs remote GPU compute.
qzcli
A command-line tool for managing GPU compute jobs on the Qizhi platform, a service for running machine-learning workloads on shared GPUs.
Tencent Cloud Infra
A command-line guide for managing Tencent Cloud services, including servers, networks, domains, certificates, storage, permissions, and monitoring. Tencent Cloud is a cloud provider, and tccli is its command-line tool.