ko-module-build

ko-module-build is a skill for Claude Code, Codex from Seeed-Projects/Seeed-Jetson-DevelopTool. It costs 58 tokens per session (1,415 once invoked), scanned D, original, MIT.

A step-by-step guide for compiling a missing Linux kernel driver module, a .ko file, on Seeed Jetson computers running JetPack 6. It uses the matching NVIDIA board-support source and loads the finished driver.

In plain words
What is it for?
Use it to build and load drivers such as USB-to-serial modules on reComputer or reServer Jetson devices.
Why use it?
It helps when hardware needs a driver that is not included in the current system. Matching the driver source to the Jetson software version avoids common build and loading failures.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/seeed-projects/seeed-jetson-developtool/ko-module-build
Any agent
npx skills add Seeed-Projects/Seeed-Jetson-DevelopTool --skill ko-module-build
Clone the repo
git clone --depth 1 https://github.com/Seeed-Projects/Seeed-Jetson-DevelopTool

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for ko-module-build

README.md
[![agentmods](https://agentmods.dev/badge/skills/seeed-projects/seeed-jetson-developtool/ko-module-build.svg)](https://agentmods.dev/skills/seeed-projects/seeed-jetson-developtool/ko-module-build)
Your own site
<a href="https://agentmods.dev/skills/seeed-projects/seeed-jetson-developtool/ko-module-build"><img src="https://agentmods.dev/badge/skills/seeed-projects/seeed-jetson-developtool/ko-module-build.svg" alt="Measured on agentmods" height="20"></a>
Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,415 The whole file, excluding the scripts and references it only reads on demand.
Security scan D 2 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00058 $0.01415
Opus 5 $0.00029 $0.00707
Sonnet 5 $0.00012 $0.00283
Haiku 4.5 $0.00006 $0.00142

Measured 4d ago against content hash 7806ca45626b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade D, and why

ko-module-build scanned grade D with 2 findings 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 find . -type f -name "*<driver_name>*"

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

sudo rm -rf /lib/modules/$(uname -r)/build
seeed_jetson_develop/skills/openclaw/ko-module-build/SKILL.md · 173 lines

How it starts

The opening of the file, as written. The whole thing — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Build a .ko Driver Module for Seeed Jetson

When a required .ko driver module is missing from reComputer/reServer, compile it directly on the Jetson device. This guide uses the pl2303 USB-to-serial driver on JetPack 6.2 (L4T 36.4.3) as an example.

Hardware: Seeed Jetson device (reComputer/reServer) Software: JetPack 6.x (L4T 36.x), internet connection


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 <driver_name> with the actual driver (e.g. pl2303) throughout.


Phase 1 — identify L4T version and target driver (~30 s)

cat /etc/nv_tegra_release

Determine the L4T version (e.g. 36.4.3 = JetPack 6.2). Find the JetPack ↔ L4T mapping at: https://developer.nvidia.com/embedded/jetpack-archive

Ask the user which driver module they need (e.g. pl2303, ch341, etc.).

[OK] when L4T version and target driver are confirmed.


Phase 2 — download and extract BSP source (~10 min)

Download public_sources.tbz2 for the matching L4T version from NVIDIA's L4T release page.

Extract all nested archives:

tar -xjf public_sources.tbz2
cd Linux_for_Tegra/source

find . -type f \( -name "*.tbz2" -o -name "*.tar.bz2" -o -name "*.tar.gz" -o -name "*.tgz" -o -name "*.tar.xz" \) -exec bash -c '
    dir=$(dirname "$1")
    filename=$(basename "$1")
    cd "$dir"
    if [[ "$filename" == *.tbz2 || "$filename" == *.tar.bz2 ]]; then
        tar -xjf "$filename"
    elif [[ "$filename" == *.tar.gz || "$filename" == *.tgz ]]; then
        tar -xzf "$filename"
    elif [[ "$filename" == *.tar.xz ]]; then
        tar -xJf "$filename"
    fi
    cd - > /dev/null
' _ {} \;

[OK] when extraction completes without errors.


Phase 3 — locate driver source file (~1 min)

sudo find . -type f -name "*<driver_name>*"
# Example: sudo find . -type f -name "*pl2303*"

Read the full file on GitHub · 173 lines

Files

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.

Changes

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.

  1. 4d ago First seen · 173 lines · 58 tokens per session scan D 7806ca45626b

Subscribe to this mod's changes

ko-module-build is a skill published in the GitHub repository Seeed-Projects/Seeed-Jetson-DevelopTool (54 stars, last pushed yesterday), licensed MIT. It adds 58 tokens to every session and 1,415 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it D with 2 findings (asks for root, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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.

obra/superpowers · 37 tokens

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.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens