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 agentlas-ai/agentlas-desktop --skill latchbio-integrationgit clone --depth 1 https://github.com/agentlas-ai/agentlas-desktopWrote 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/agentlas-ai/agentlas-desktop/latchbio-integration)<a href="https://agentmods.dev/skills/agentlas-ai/agentlas-desktop/latchbio-integration"><img src="https://agentmods.dev/badge/skills/agentlas-ai/agentlas-desktop/latchbio-integration/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/agentlas-ai/agentlas-desktop/latchbio-integration"><img src="https://agentmods.dev/badge/skills/agentlas-ai/agentlas-desktop/latchbio-integration.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.00076 | $0.02242 |
| Opus 5.5 | $0.00030 | $0.00897 |
| Sonnet 5.5 | $0.00015 | $0.00448 |
| Haiku 4.5 | $0.00008 | $0.00224 |
Grade A, and why
latchbio-integration 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
with `subprocess.run(..., check=True)`. This is a copy
100% identical to latchbio-integration — 34 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LatchBio Integration
Current Baseline
This skill targets Latch SDK 2.76.8, released July 10, 2026. The package metadata supports Python 3.9–3.12 and declares Python 3.9+.
Treat the installed package and its changelog as authoritative when a guide disagrees with the SDK. Some Latch guides retain older Python ranges or compatibility-specific pre-release pins, especially the Snakemake v2 tutorial. Never combine commands or imports from different tracks without checking their version requirements.
When to Use
Use this skill to:
- Create or maintain Python SDK workflows and task graphs
- Package and register Python, Nextflow, or Snakemake pipelines
- Configure task CPU, memory, storage, GPU, caching, retries, and timeouts
- Work with Latch Data through
LPath,LatchFile,LatchDir, or the CLI - Read or update Latch Registry projects, tables, and records
- Design workflow forms, launch plans, samplesheets, messages, and result links
- Stage and debug workflow images with
latch register --stagingandlatch develop - Launch and monitor workflows through Python or Latch MCP
- Discover and use ready-to-run Latch workflows
Route to the Right Reference
Read only the references needed for the task:
| Need | Reference |
|---|---|
| Python workflows, tasks, maps, conditions, caching | references/workflow-creation.md |
LPath, legacy file types, Latch URLs, data CLI |
references/data-management.md |
| Registry reads, transactions, samplesheets | references/registry.md |
| CPU, memory, storage, GPU, dynamic resources | references/resource-configuration.md |
| Nextflow and Snakemake packaging | references/nextflow-snakemake.md |
| Metadata, forms, launch plans, messages, automations | references/ui-and-automation.md |
| Registration, development, execution, monitoring | references/operations-and-debugging.md |
Ready-to-use workflows and latch.verified |
references/verified-workflows.md |
| Remote MCP setup and tool workflow | references/latch-mcp.md |
What ships with it
10 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.
- references/data-management.md 7.2 KB
- references/latch-mcp.md 4.4 KB
- references/nextflow-snakemake.md 8.4 KB
- references/operations-and-debugging.md 8.3 KB
- references/registry.md 7.3 KB
- references/resource-configuration.md 7.4 KB
- references/ui-and-automation.md 9.3 KB
- references/verified-workflows.md 6.5 KB
- references/workflow-creation.md 8.0 KB
- scripts/inspect_latch_sdk.py 8.9 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 · 245 lines · 76 tokens per session scan A f9607ea51cec
latchbio-integration is a skill published in the GitHub repository agentlas-ai/agentlas-desktop (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 76 tokens to every session and 2,242 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (runs shell commands). It is 100% identical to latchbio-integration, differing in 34 lines, and is treated as a copy.
Other skills, from other repositories
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.
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.
winui-wpf-migration
Migrate or port a WPF app to WinUI 3: namespaces (System.Windows to Microsoft.UI.Xaml), control mapping (DataGrid, WrapPanel, TabControl), Dispatcher to DispatcherQueue, imaging, MVVM with CommunityToolkit.Mvvm, ThemeResource. Use when converting WPF code or fixing migration build errors.
remote-compute-ssh
Run Feynman research jobs on SSH, Slurm, or lab hosts. Use when a task needs remote host setup, job submission, log harvest, artifact sync, or GPU/cluster execution outside Modal.