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/ethercat-setupnpx skills add Seeed-Projects/Seeed-Jetson-DevelopTool --skill ethercat-setupgit clone --depth 1 https://github.com/Seeed-Projects/Seeed-Jetson-DevelopToolWhat 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 | $0.00065 | $0.01240 |
| Opus 5 | $0.00032 | $0.00620 |
| Sonnet 5 | $0.00013 | $0.00248 |
| Haiku 4.5 | $0.00006 | $0.00124 |
Grade B, and why
ethercat-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 2d 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 apt update How it starts
The opening of the file, as written. The whole thing — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EtherCAT Setup on Jetson with EtherLab Master
Execution model
Run one phase at a time. After each phase:
- Relay all command output to the user.
- If output contains
[STOP]→ stop immediately, consult the failure decision tree below. - If output ends with
[OK]→ tell the user "Phase N complete" and proceed to the next phase.
Prerequisites
| Requirement | Details |
|---|---|
| Hardware | reComputer Robotics J401 (or compatible Jetson) as EtherCAT master |
| Slave device | EtherCAT slave (e.g. MyActuator X4) with external power |
| JetPack | 6.2 (L4T 36.4.3) |
| Cable | Ethernet cable + adapter if slave uses 4-pin interface (Tx+, Tx–, Rx+, Rx–) |
Most slave devices require additional external power after physical Ethernet connection.
Phase 1 — Hardware connection (~2 min)
Connect the Jetson Ethernet interface directly to the EtherCAT slave device. If the slave uses a 4-pin interface, use an Ethernet-to-4-pin adapter.
Identify the Ethernet interface name:
ifconfig
Note the interface name (e.g. eno1). This will be used in subsequent configuration.
[OK] — proceed to Phase 2.
Phase 2 — Install EtherCAT driver (~5–10 min)
Install build dependencies and compile the EtherLab EtherCAT master:
sudo apt update
sudo apt install build-essential cmake libtool autoconf automake
git clone https://gitlab.com/etherlab.org/ethercat.git
cd ethercat
./bootstrap
./configure --sysconfdir=/etc
make all modules
sudo make modules_install install
sudo depmod -a
Verify the kernel modules are loaded:
sudo lsmod | grep "ec_"
Expected: ec_master and ec_generic modules listed.
[OK] — proceed to Phase 3. [STOP] if modules not found.
Phase 3 — Configure EtherCAT master (~2 min)
Edit the configuration file:
sudo vim /etc/ethercat.conf
Set these parameters (replace eno1 with your interface name):
MASTER0_DEVICE="eno1"
DEVICE_MODULES="generic"
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.
- 2d ago First seen · 192 lines · 65 tokens per session scan B 09337623b67c
ethercat-setup is a skill published in the GitHub repository Seeed-Projects/Seeed-Jetson-DevelopTool (54 stars, last pushed 2d ago), licensed MIT. It adds 65 tokens to every session and 1,240 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.