opentrons-integration

opentrons-integration is a skill for Claude Code from agentlas-ai/agentlas-desktop. It costs 79 tokens per session (3,395 once invoked), scanned A, a copy of opentrons-integration, Apache-2.0.

A guide and toolkit for writing and checking Python protocols for Opentrons Flex and OT-2 laboratory robots. It covers deck setup, labware, pipettes, modules, runtime settings, simulation, and deployment.

In plain words
What is it for?
Use it to create, review, migrate, simulate, or troubleshoot liquid-handling protocols and robot-specific hardware or deck configurations.
Why use it?
Robot protocols control physical equipment, so code that merely runs or simulates is not enough to establish that a run is safe. The workflow adds version checks, simulation, and application analysis before live execution.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it to create, review, migrate, simulate, or troubleshoot liquid-handling protocols and robot-specific hardware or deck configurations.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/agentlas-ai/agentlas-desktop/opentrons-integration
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 agentlas-ai/agentlas-desktop --skill opentrons-integration
Clone the repo
git clone --depth 1 https://github.com/agentlas-ai/agentlas-desktop

Made for: Claude Code.

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 opentrons-integration

README.md
[![agentmods](https://agentmods.dev/badge/skills/agentlas-ai/agentlas-desktop/opentrons-integration/github.svg)](https://agentmods.dev/skills/agentlas-ai/agentlas-desktop/opentrons-integration)
Your own site
<a href="https://agentmods.dev/skills/agentlas-ai/agentlas-desktop/opentrons-integration"><img src="https://agentmods.dev/badge/skills/agentlas-ai/agentlas-desktop/opentrons-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.

agentmods 80×15 button for opentrons-integration

Your own site · 80×15
<a href="https://agentmods.dev/skills/agentlas-ai/agentlas-desktop/opentrons-integration"><img src="https://agentmods.dev/badge/skills/agentlas-ai/agentlas-desktop/opentrons-integration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 79 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,395 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 100% copy Near-identical to another mod 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.00079 $0.03395
Opus 5.5 $0.00032 $0.01358
Sonnet 5.5 $0.00016 $0.00679
Haiku 4.5 $0.00008 $0.00340

Measured 1mo ago against content hash 6d647ecd7205, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

opentrons-integration 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 1mo ago.

The scan reads SKILL.md. This mod also ships 6 executable files (scripts/absorbance_reader_template.py, scripts/basic_protocol_template.py, scripts/ot2_basic_protocol_template.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Origin

This is a copy

100% identical to opentrons-integration — 53 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.

plugins/agentlas-science-skills/skills/opentrons-integration/SKILL.md · 340 lines

How it starts

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

Opentrons Integration

Overview

Create production-minded Python Protocol API v2 protocols for Opentrons Flex and OT-2. This skill covers protocol structure, hardware and deck configuration, liquid handling, runtime customization, module control, simulation, and safe deployment.

The verified baseline as of 2026-07-23 is:

  • opentrons==9.1.1 for reproducible Flex simulation.
  • opentrons==9.0.0 for local OT-2 API 2.28 compatibility simulation.
  • Flex supports API levels 2.15 through 2.29 on current software.
  • OT-2 supports API levels 2.0 through 2.28 on current software.
  • API 2.29 is Flex-only at this baseline. Do not put 2.29 in an OT-2 protocol.

Read references/sources.md for the upstream documentation used for this snapshot. Recheck the official versioning page before targeting newer robot software.

Safety Boundary

Opentrons protocols control physical equipment. Never treat successful Python syntax or local simulation as permission to run on a robot.

Before live execution:

  1. Simulate locally with the same pinned opentrons version used for authoring.
  2. Import the protocol into the correct Opentrons App and require successful analysis.
  3. Verify robot model, software, pipettes, mounts, modules, adapters, labware definitions, deck fixtures, tip count, source volumes, dead volumes, and destination capacity.
  4. Review the run preview and deck map with the operator.
  5. Perform a slow dry run with nonhazardous liquid when geometry, custom labware, partial tip pickup, or gripper moves are new.
  6. Keep the emergency stop accessible and follow site-specific biosafety, chemical-safety, and contamination-control procedures.

Simulation cannot verify physical calibration, liquid properties, meniscus behavior, labware manufacturing tolerances, cap or seal removal, tubing, or all possible collisions.

Choose the Right Interface

Use this skill for Python files imported into the Opentrons App and run through the Protocol API.

  • Use Protocol Designer for supported no-code workflows.
  • Use PyLabRobot for a hardware-agnostic workflow spanning vendors.
  • Treat the robot's HTTP API as a separate integration surface. If direct HTTP control is explicitly required, use the OpenAPI document served by the target robot and do not infer endpoints from Protocol API methods.

Read the full file on GitHub · 340 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. 1mo ago First seen · 340 lines · 79 tokens per session scan A 6d647ecd7205

Subscribe to this mod's changes

opentrons-integration is a skill published in the GitHub repository agentlas-ai/agentlas-desktop (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 79 tokens to every session and 3,395 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to opentrons-integration, differing in 53 lines, and is treated as a copy.

Related

Other skills, from other repositories

evaluating-cosmos-policy

Evaluates NVIDIA Cosmos Policy on LIBERO and RoboCasa simulation environments. Use when setting up cosmos-policy for robot manipulation evaluation, running headless GPU evaluations with EGL rendering, or profiling inference latency on cluster or local GPU machines.

Orchestra-Research/AI-Research-SKILLs · 51 tokens

i4h-catheter-navigation

Overview of workflows/catheternavigation/ (fluorosim DRR, XPBD physics, vasculature digital twin). Use when the user asks what the catheter navigation workflow is, what's supported, or where to start.

NVIDIA/skills · 55 tokens

opentrons-integration

Official Opentrons Protocol API for OT-2 and Flex robots. Use when writing protocols specifically for Opentrons hardware with full access to Protocol API v2 features. Best for production Opentrons protocols, official API compatibility. For multi-vendor automation or broader equipment control use pylabrobot.

synthetic-sciences/openscience · 66 tokens

pylabrobot

Vendor-agnostic lab automation framework. Use when controlling multiple equipment types (Hamilton, Tecan, Opentrons, plate readers, pumps) or needing unified programming across different vendors. Best for complex workflows, multi-vendor setups, simulation. For Opentrons-only protocols with official API…

synthetic-sciences/openscience · 73 tokens

vss-generate-video-calibration

Use this skill when running or tuning AutoMagicCalib on local MP4s, RTSP, or the bundled sample dataset, or when deploying vss-auto-calibration. Do not use for non-AMC calibration or runtime analytics.

NVIDIA-AI-Blueprints/video-search-and-summarization · 55 tokens

spice-sim

Add or run an ngspice-backed Zener testbench with pcb sim.

diodeinc/pcb · 22 tokens