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 system-log-j30-j40git 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/system-log-j30-j40)<a href="https://agentmods.dev/skills/seeed-projects/seeed-jetson-developtool/system-log-j30-j40"><img src="https://agentmods.dev/badge/skills/seeed-projects/seeed-jetson-developtool/system-log-j30-j40/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/system-log-j30-j40"><img src="https://agentmods.dev/badge/skills/seeed-projects/seeed-jetson-developtool/system-log-j30-j40.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, 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 67 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.
- medium Privilege Escalation · line 80 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.00056 | $0.00728 |
| Opus 5 | $0.00028 | $0.00364 |
| Sonnet 5 | $0.00011 | $0.00146 |
| Haiku 4.5 | $0.00006 | $0.00073 |
Grade B, and why
system-log-j30-j40 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 5d 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 reboot How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Get System Log of reComputer J30/J40
Execution model
Run one phase at a time. After each phase, verify the expected result before continuing.
- If a phase succeeds → print
[OK]and move to the next phase. - If a phase fails → print
[STOP], consult the failure decision tree, and ask the user before retrying.
Phase 1 — Verify prerequisites
Required hardware:
- reComputer J4012, J4011, J3010, or J3011
- USB to Serial (TTL) module (e.g., CH340G)
- Host PC with a serial port debugging tool (PuTTY, XShell, or MobaXterm)
Install a serial debugging tool on the host PC if not already available.
Phase 2 — Hardware connection
- Connect the J15 interface pins on the reComputer to the USB2TTL module:
- TX → RX
- RX → TX
- GND → GND
- Connect the USB2TTL module to the host PC via USB.
Expected: USB2TTL module recognized by the host PC.
Phase 3 — Identify the serial port
On the host PC, find the USB2TTL device identifier:
# Linux
ls /dev/ttyUSB* /dev/ttyACM*
dmesg | tail -20
On Windows: Open Device Manager and look under "Ports (COM & LPT)" for the COM port number.
Expected: Serial device identified (e.g., /dev/ttyUSB0 on Linux or COM3 on Windows).
Phase 4 — Configure serial debugging tool
Open your serial debugging tool and configure:
- Serial port: the port identified in Phase 3
- Baud rate:
115200 - Data bits: 8
- Stop bits: 1
- Parity: None
- Flow control: None
Click Connect / Open to start the serial session.
Expected: Serial session opens without errors.
Phase 5 — Capture boot logs
Power on (or reboot) the Jetson device. The boot logs should appear in the serial debugging tool window.
# If you need to reboot the Jetson remotely
sudo reboot
Expected: System boot logs stream in the serial terminal, showing kernel messages and boot sequence.
Failure decision tree
| Symptom | Likely cause | Suggested fix |
|---|---|---|
| No serial device found on host | USB2TTL driver not installed | Install CH340 or CP2102 driver for your OS |
| Serial port opens but no output | TX/RX wires swapped | Swap TX and RX connections between J15 and USB2TTL |
| Garbled text in terminal | Wrong baud rate | Ensure baud rate is set to 115200 |
| No output on power-on | Wrong pins on J15 header | Verify pin mapping from reComputer J30/J40 datasheet |
| Permission denied on Linux | User not in dialout group | sudo usermod -aG dialout $USER then re-login |
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.
- 5d ago First seen · 85 lines · 56 tokens per session scan B 65d0ad54ea11
system-log-j30-j40 is a skill published in the GitHub repository Seeed-Projects/Seeed-Jetson-DevelopTool (54 stars, last pushed today), licensed MIT. It adds 56 tokens to every session and 728 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-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…
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…
doca-flow
Build and debug DOCA Flow applications on supported NVIDIA NICs/DPUs: define match/action pipes, initialize ports and representors, choose forwarding targets, validate pipes before hardware programming, read counters, match the Flow version to the installed DOCA release, and diagnose Flow API errors. Trigger on DOCA…
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 a device is unreachable, a user reports connectivity problems, an interface…