Feynman is an open-source AI research agent that helps users investigate topics with language models. It supports local model providers and hosted model authentication through its setup process. The catalogue contains skills, agents, and instructions that extend Feynman’s workflows.
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 companion-inc/feynman --skill remote-compute-sshgit clone --depth 1 https://github.com/companion-inc/feynmanWrote 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/companion-inc/feynman/remote-compute-ssh)<a href="https://agentmods.dev/skills/companion-inc/feynman/remote-compute-ssh"><img src="https://agentmods.dev/badge/skills/companion-inc/feynman/remote-compute-ssh.svg" alt="Measured on agentmods" 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.00048 | $0.00202 |
| Opus 5 | $0.00024 | $0.00101 |
| Sonnet 5 | $0.00010 | $0.00040 |
| Haiku 4.5 | $0.00005 | $0.00020 |
Grade A, and why
remote-compute-ssh 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 7d 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.
What it actually says
Remote Compute: SSH
Use this skill for lab machines, SSH hosts, and Slurm-style research jobs.
Workflow:
- Record host alias, scheduler, working directory, environment module/conda/container needs, data paths, and artifact return path.
- Verify access and a tiny smoke command before the main job.
- Submit with a bounded script that logs package versions, hardware, command, and seed.
- Harvest stdout/stderr, job id, exit status, produced artifacts, and checksums into the Feynman workspace.
- Mark failed or partial jobs honestly; do not fabricate remote artifacts from local expectations.
Keep remote credentials and private paths out of user-facing summaries unless they are needed for reproducibility.
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.
- 7d ago First seen · 19 lines · 48 tokens per session scan A 0617f220a1c1
remote-compute-ssh is a skill published in the GitHub repository companion-inc/feynman (8,870 stars, last pushed 11d ago), licensed MIT. It adds 48 tokens to every session and 202 once invoked, about $0.0002 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-30.
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.
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.
validate-gpu-cluster
Check whether a DeepOps-deployed Slurm or Kubernetes GPU cluster is healthy and report a machine-readable verdict. Use for health checks, post-deploy verification, "is the cluster working?" questions, and after any node or driver change.