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 agentmods add skills/seeed-projects/seeed-jetson-developtool/lerobot-env-setupnpx skills add Seeed-Projects/Seeed-Jetson-DevelopTool --skill lerobot-env-setupgit clone --depth 1 https://github.com/Seeed-Projects/Seeed-Jetson-DevelopToolWrote 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/seeed-projects/seeed-jetson-developtool/lerobot-env-setup)<a href="https://agentmods.dev/skills/seeed-projects/seeed-jetson-developtool/lerobot-env-setup"><img src="https://agentmods.dev/badge/skills/seeed-projects/seeed-jetson-developtool/lerobot-env-setup.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.00089 | $0.01042 |
| Opus 5 | $0.00044 | $0.00521 |
| Sonnet 5 | $0.00018 | $0.00208 |
| Haiku 4.5 | $0.00009 | $0.00104 |
Grade B, and why
lerobot-env-setup scanned grade B 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 6d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
if dpkg -l brltty 2>/dev/null | grep -q '^ii'; then sudo apt remove brltty; fi How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LeRobot Environment Setup (Jetson / SO-ARM)
Execution model
Run the install script one phase at a time. After each phase:
- Relay the output to the user (show
[install]lines) - If it printed
[STOP]→ stop, follow the failure decision tree below - If it ended with
[install] Step N:or[OK]→ proceed to next phase
Why phases? The torch download is ~254 MB and takes 10–20 min. Running everything in one call risks silent timeout. Phases give the user visibility and a recovery point at each step.
Phase commands
Replace <ENV> with the env name the user requested (default: lerobot).
All phases use the same script — the script is idempotent; already-done steps
are skipped automatically.
Phase 1 — Environment + clone (fast, ~1 min)
bash ~/.agents/skills/lerobot-env-setup/scripts/install_lerobot.sh \
--env <ENV> --robot-type so-arm --phase env
Phase 2 — Download wheels (slow, 10–20 min, shows % progress)
bash ~/.agents/skills/lerobot-env-setup/scripts/install_lerobot.sh \
--env <ENV> --robot-type so-arm --phase download
Phase 3 — Install torch + verify CUDA (fast, ~2 min)
bash ~/.agents/skills/lerobot-env-setup/scripts/install_lerobot.sh \
--env <ENV> --robot-type so-arm --phase torch-pre
Phase 4 — opencv / ffmpeg / numpy + lerobot editable (medium, ~5 min)
bash ~/.agents/skills/lerobot-env-setup/scripts/install_lerobot.sh \
--env <ENV> --robot-type so-arm --phase deps
Phase 5 — Reinstall torch + validate (fast, ~2 min)
bash ~/.agents/skills/lerobot-env-setup/scripts/install_lerobot.sh \
--env <ENV> --robot-type so-arm --phase torch-post
Failure decision tree
| Output | Action |
|---|---|
[STOP] conda not found |
Ask user: "Please confirm miniconda is installed at ~/miniconda3 or give path" |
[STOP] conda env ... exists but has Python X.Y |
Should not happen (script auto-fixes). If seen, run conda env remove -n <ENV> then re-run phase 1 |
[STOP] torch wheel not found after download |
SharePoint URL expired. Ask user to re-share wheel files or place them manually in ~/wheels/ |
[STOP] torch.cuda.is_available() = False |
Wheel may be corrupt. Run: rm ~/wheels/*.whl then re-run phase 2 and 3 |
[FAIL] Some checks failed |
Read which line shows ✗, then check references/conflict_resolution_playbook.md for F1–F7 |
| Script hangs with no output >5 min | Report to user, ask whether to cancel and retry |
What ships with it
8 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/conflict_resolution_playbook.md 3.6 KB
- references/dependency_mapping_rules.md 2.8 KB
- references/jetpack_compatibility_matrix.json 1.9 KB
- references/lerobot_env_setup.md 5.3 KB
- scripts/analyze_compatibility.py 12 KB runs code
- scripts/collect_jetson_facts.sh 8.0 KB runs code
- scripts/download_wheels.py 3.8 KB runs code
- scripts/install_lerobot.sh 10 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.
- 6d ago First seen · 96 lines · 89 tokens per session scan B a9f308b5b819
lerobot-env-setup is a skill published in the GitHub repository Seeed-Projects/Seeed-Jetson-DevelopTool (54 stars, last pushed yesterday), licensed MIT. It adds 89 tokens to every session and 1,042 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
jetson-diagnostic
Read-only Jetson health snapshot for identity, memory, GPU, thermal, power, storage, services, and top processes.
doca-socket-relay
Use this skill when the operator is driving the DOCA Socket Relay to bridge a socket-oriented host application onto a BlueField DPU peer without rewriting it — picking the deployment shape (in-process, sidecar, or BlueField service container), configuring the host-side socket and the DPU-side forwarding endpoint…
offensive-z-wave
Z-Wave attack methodology — sniffing with Z-Force / EZ-Wave / RTL-SDR + ZniffMobile, S0 (legacy) network-key derivation flaw and key reuse, S2 (modern) ECDH commissioning analysis, replay/injection on unauthenticated nodes, default-key brute-force on test deployments, and home-automation hub pivots. Use when targeting…
hsb-flash
Flash the FPGA on an HSB board connected to an NVIDIA devkit. Supports HSB Lattice boards (FPGA versions 2407, 2412, 2507, 2510) and Leopard Imaging VB1940 "all-in-one" cameras (FPGA versions 2507, 2510). Uses release-specific YAML manifests and board-type-specific program commands. Lattice and VB1940 commands must…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.