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 Seeed-Projects/Seeed-Jetson-DevelopTool --skill usb-timeout-during-flashinggit 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/usb-timeout-during-flashing)<a href="https://agentmods.dev/skills/seeed-projects/seeed-jetson-developtool/usb-timeout-during-flashing"><img src="https://agentmods.dev/badge/skills/seeed-projects/seeed-jetson-developtool/usb-timeout-during-flashing/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/seeed-projects/seeed-jetson-developtool/usb-timeout-during-flashing"><img src="https://agentmods.dev/badge/skills/seeed-projects/seeed-jetson-developtool/usb-timeout-during-flashing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Privilege Escalation · line 85 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
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.00000 | $0.01051 |
| Opus 5.5 | $0.00000 | $0.00420 |
| Sonnet 5.5 | $0.00000 | $0.00210 |
| Haiku 4.5 | $0.00000 | $0.00105 |
Grade B, and why
usb-timeout-during-flashing 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 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo ./flash.sh <board-config> mmcblk0p1 How it starts
The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
USB Timeout During Flashing
USB timeouts during JetPack flashing are almost always caused by one of five environmental issues — not a firmware bug. Work through the checklist in order before retrying the flash script.
Execution model
This is a diagnostic checklist, not a scripted install. Work through each check in order:
- If a check reveals the problem → apply the fix, then restart the flash script from the beginning.
- If a check passes → move to the next one.
- Use the failure decision tree to map your symptom directly to a fix.
Diagnostic checklist
Check 1 — Ubuntu VM USB instability
If you are flashing from inside a VirtualBox or VMware VM, USB passthrough is unreliable and is the most common cause of timeouts.
Verify:
- The Jetson USB device is exclusively assigned to the VM (not shared with the host).
- USB 3.0 controller is enabled in VM settings (not USB 2.0 emulation).
- No other USB devices are competing for bandwidth during the flash.
Fix: Flash from a native Ubuntu install (bare-metal or live USB) instead of a VM whenever possible.
Check 2 — Insufficient DC power
The Jetson draws significant current during flashing. An underpowered supply causes USB enumeration to drop mid-flash.
Verify:
- Power supply meets the board's rated wattage (check your reComputer/Jetson model spec sheet).
- No other high-draw peripherals (drives, cameras) are connected during flashing.
- The power LED stays solid — a flickering LED indicates a power issue.
Fix: Use the official power adapter for your board. Disconnect all non-essential peripherals.
Check 3 — Bad or incompatible Type-C cable
Not all USB-C cables support USB 2.0 data. Charging-only cables and cables over 1.5 m are common culprits.
Verify:
- Cable is rated for USB 2.0 data (not charge-only).
- Cable length is under 1.5 m.
- Try a different cable if in doubt — this is the fastest check to eliminate.
Fix: Replace with a short (<1 m), data-rated USB-C cable.
Check 4 — USB hub interference
What ships with it
2 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.
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 · 109 lines · 0 tokens per session scan B 601d3f71b80d
usb-timeout-during-flashing is a skill published in the GitHub repository Seeed-Projects/Seeed-Jetson-DevelopTool (56 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,051 tokens. 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-09-03.
Other skills, from other repositories
gke-ai-troubleshooting-tpu-dynamic-slices-monitoring
Monitors, troubleshoots, and manages GKE TPU Dynamic Slices custom resources. Use when checking TPU slice lifecycle states, troubleshooting slice provisioning failures, validating single-slice or multi-slice (JobSet) workload manifests, or safely patching stuck finalizers and disabling the slice controller. Don't use…
gke-ai-troubleshooting-tpu-vbar-oom
Diagnoses and prevents vbarcontrolagent segfaults, out-of-memory (OOM) errors, and TPU device initialization failures on TPU v6e nodes in GKE caused by race conditions during TPU device resets or high-frequency metrics polling. Use when troubleshooting vbarcontrolagent crashes, memory cgroup OOMs in serial console…
doca-flow
DOCA Flow packet steering on NVIDIA NICs/DPUs, linked into a C application: match/action pipes, ports, representors, forwarding, hairpin, counters. Trigger on packet steering, classifier, rule-matching, representor, hairpin or 5-tuple-to-queue questions even when "DOCA Flow" is not named. Also covers pipe validation…
competition-firmware-layout
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for firmware images, partition tables, boot chains, update packages, extracted filesystems, embedded configs, and device-facing trust boundaries. Use when the user asks to unpack firmware, map partition layout, inspect bootloader or init…
diagnose-driver-install
Diagnose NVIDIA driver installation failures on DeepOps-managed nodes — nvidia-smi errors, "No devices were found", DKMS build failures, or GPU pods crash-looping. Use before reinstalling anything.
catc-troubleshoot
Catalyst Center troubleshooting workflows - device unreachable investigation, client connectivity issues, interface down analysis, site-wide outage triage, wireless roaming problems, integration with pyATS for CLI-level diagnostics. Use when the device is managed by Catalyst Center and you want its…