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/bsp-source-buildnpx skills add Seeed-Projects/Seeed-Jetson-DevelopTool --skill bsp-source-buildgit 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/bsp-source-build)<a href="https://agentmods.dev/skills/seeed-projects/seeed-jetson-developtool/bsp-source-build"><img src="https://agentmods.dev/badge/skills/seeed-projects/seeed-jetson-developtool/bsp-source-build.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 | $0.00048 | $0.01441 |
| Opus 5 | $0.00024 | $0.00720 |
| Sonnet 5 | $0.00010 | $0.00288 |
| Haiku 4.5 | $0.00005 | $0.00144 |
Grade B, and why
bsp-source-build 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 4d 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-get update How it starts
The opening of the file, as written. The whole thing — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build Seeed Jetson BSP from Source
Obtain the BSP source code for Seeed's Jetson products, overlay Seeed's customizations from GitHub, compile the kernel, and flash onto the device.
Hardware: Seeed Jetson device (reComputer/reServer), USB cable for flashing Software: Ubuntu 20.04 or 22.04 host PC (native)
Source: https://github.com/Seeed-Studio/Linux_for_Tegra
Execution model
Run one phase at a time. After each phase:
- If output contains
[STOP]→ stop immediately, consult the failure decision tree - If output ends with
[OK]→ tell the user "Phase N complete" and proceed
Replace <L4T_VERSION> with the target version (e.g. 36.4.3) throughout.
Phase 1 — install build dependencies (~2 min)
sudo apt-get update
sudo apt-get install -y build-essential flex bison libssl-dev \
sshpass abootimg nfs-kernel-server libxml2-utils qemu-user-static git-lfs
[OK] when all packages install without errors.
Phase 2 — download & extract NVIDIA BSP + rootfs (~10 min)
Download from https://developer.nvidia.com/embedded/linux-tegra-archive:
- L4T Driver Package (BSP):
Jetson_Linux_r<L4T_VERSION>_aarch64.tbz2 - Sample Root Filesystem:
Tegra_Linux_Sample-Root-Filesystem_r<L4T_VERSION>_aarch64.tbz2
tar xf Jetson_Linux_r<L4T_VERSION>_aarch64.tbz2
sudo tar xpf Tegra_Linux_Sample-Root-Filesystem_r<L4T_VERSION>_aarch64.tbz2 \
-C Linux_for_Tegra/rootfs/
[OK] when Linux_for_Tegra/rootfs/ is populated.
Phase 3 — sync NVIDIA source & overlay Seeed patches (~15 min)
cd Linux_for_Tegra/source/
./source_sync.sh -t jetson_<L4T_VERSION>
cd ../..
Clone Seeed's BSP overlay:
mkdir -p github/Linux_for_Tegra
git clone https://github.com/Seeed-Studio/Linux_for_Tegra.git \
-b r<L4T_VERSION> --depth=1 github/Linux_for_Tegra
Overlay Seeed files:
cp -r github/Linux_for_Tegra/* Linux_for_Tegra/
Apply binaries:
cd Linux_for_Tegra
sudo ./apply_binaries.sh
[OK] when apply_binaries.sh completes.
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.
- 4d ago First seen · 180 lines · 48 tokens per session scan B ac2630e0a572
bsp-source-build is a skill published in the GitHub repository Seeed-Projects/Seeed-Jetson-DevelopTool (54 stars, last pushed yesterday), licensed MIT. It adds 48 tokens to every session and 1,441 once invoked, about $0.0002 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
remote-mac
Remote Macs: MacBooks, Mac Studios, hosted claw Macs, Tailscale, SSH, and OpenClaw.
hyperpod-version-checker
Check and compare software component versions on SageMaker HyperPod cluster nodes - NVIDIA drivers, CUDA toolkit, cuDNN, NCCL, EFA, AWS OFI NCCL, GDRCopy, MPI, Neuron SDK (Trainium/Inferentia), Python, and PyTorch. Use when checking component versions, verifying CUDA/driver compatibility, detecting version mismatches…
hcp-create-agent
Use this skill when you need to deploy HyperShift clusters on bare metal, edge environments, or disconnected infrastructures using pre-provisioned agents.
REPLACE-WITH-PLATFORM-NAME
Where and how GPU jobs run on this platform. One-to-three-sentence summary. Use when the user asks to "deploy on REPLACE-PLATFORM", "run on REPLACE-PLATFORM", or mentions the platform's distinctive concepts (e.g., resource shape, instance, node group).
pwn-aws-iot
Drive PWN::AWS::IoT from pwneval.
pwn-aws-iotdataplane
Drive PWN::AWS::IoTDataPlane from pwneval.