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 open-vela/.claude --skill openvela-buildgit clone --depth 1 https://github.com/open-vela/.claudeWrote 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/open-vela/.claude/openvela-build)<a href="https://agentmods.dev/skills/open-vela/.claude/openvela-build"><img src="https://agentmods.dev/badge/skills/open-vela/.claude/openvela-build/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/open-vela/.claude/openvela-build"><img src="https://agentmods.dev/badge/skills/open-vela/.claude/openvela-build.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00049 | $0.00932 |
| Opus 5 | $0.00024 | $0.00466 |
| Sonnet 5 | $0.00010 | $0.00186 |
| Haiku 4.5 | $0.00005 | $0.00093 |
Grade C, and why
openvela-build scanned grade C 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 12d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf <OUTPUT_DIR> How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
openvela Build
编译 openvela 固件、修改内核配置、运行模拟器。
默认目标
默认编译目标为 goldfish-arm64-v8a-ap(64 位 ARM 模拟器):
CONFIG_PATH=vendor/openvela/boards/vela/configs/goldfish-arm64-v8a-ap/
OUTPUT_DIR=cmake_out/vela_goldfish-arm64-v8a-ap/
如果用户指定了其他板级配置路径,替换上述路径即可。
命令
编译
./build.sh <CONFIG_PATH> --cmake -j$(nproc)
示例:
./build.sh vendor/openvela/boards/vela/configs/goldfish-arm64-v8a-ap/ --cmake -j$(nproc)
成功标志: 输出 #### build completed successfully
编译产物: <OUTPUT_DIR>/nuttx(ELF)、<OUTPUT_DIR>/vela_ap.bin
修改内核配置(menuconfig)
./build.sh <CONFIG_PATH> --cmake menuconfig
menuconfig 是交互式 TUI 界面,不能在 AI 终端中直接运行。提示用户在自己的终端中执行。
修改配置后保存会自动更新 .config。如需持久化到 defconfig:
./build.sh <CONFIG_PATH> --cmake savedefconfig
运行模拟器
./emulator.sh <OUTPUT_DIR>
示例:
./emulator.sh cmake_out/vela_goldfish-arm64-v8a-ap/
成功标志: 出现 goldfish-armv8a-ap> NSH 提示符
清理编译
rm -rf <OUTPUT_DIR>
全量清理后重新编译:
rm -rf cmake_out/vela_goldfish-arm64-v8a-ap/ && ./build.sh vendor/openvela/boards/vela/configs/goldfish-arm64-v8a-ap/ --cmake -j$(nproc)
编译流程
- 用户指定或确认目标配置路径
- 执行
./build.sh <path> --cmake -j$(nproc) - 检查输出最后几行是否包含
build completed successfully - 如果编译失败,分析错误日志并尝试修复(最多 3 轮)
编译失败处理
| 错误类型 | 特征 | 处理 |
|---|---|---|
| 代码错误 | error: + 本驱动文件名 |
自动修复代码,重新编译 |
| 配置缺失 | undefined reference + CONFIG 相关 |
提示用户 menuconfig 开启 |
| 工具链问题 | command not found |
提示用户安装工具链 |
| 缓存问题 | 奇怪的链接错误 | rm -rf <OUTPUT_DIR> 后重编 |
启用新驱动的 CONFIG
如果需要临时启用某个 CONFIG 进行编译验证:
# 方法 1: 直接追加到 defconfig(推荐)
echo "CONFIG_SENSORS_BME680=y" >> <CONFIG_PATH>/defconfig
# 方法 2: 用 sed 修改 .config(临时,不持久化)
sed -i 's/# CONFIG_SENSORS_BME680 is not set/CONFIG_SENSORS_BME680=y/' <OUTPUT_DIR>/.config
修改后重新编译即可。
常用配置路径
| 目标 | 配置路径 |
|---|---|
| goldfish-arm64 (推荐) | vendor/openvela/boards/vela/configs/goldfish-arm64-v8a-ap/ |
| goldfish-arm32 | vendor/openvela/boards/vela/configs/goldfish-armeabi-v7a-ap/ |
| 自定义板级 | vendor/<vendor>/boards/<chip>/<board>/configs/<config>/ |
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.
- 12d ago First seen · 112 lines · 49 tokens per session scan C 35285fbea20a
openvela-build is a skill published in the GitHub repository open-vela/.claude (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 49 tokens to every session and 932 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
jetson-diagnostic
Read-only Jetson health snapshot for identity, memory, GPU, thermal, power, storage, services, and top processes.
doca-socket-relay
Use this skill when the operator is driving the DOCA Socket Relay to bridge a socket-oriented host application onto a BlueField DPU peer without rewriting it — picking the deployment shape (in-process, sidecar, or BlueField service container), configuring the host-side socket and the DPU-side forwarding endpoint…
offensive-z-wave
Z-Wave attack methodology — sniffing with Z-Force / EZ-Wave / RTL-SDR + ZniffMobile, S0 (legacy) network-key derivation flaw and key reuse, S2 (modern) ECDH commissioning analysis, replay/injection on unauthenticated nodes, default-key brute-force on test deployments, and home-automation hub pivots. Use when targeting…
hsb-flash
Flash the FPGA on an HSB board connected to an NVIDIA devkit. Supports HSB Lattice boards (FPGA versions 2407, 2412, 2507, 2510) and Leopard Imaging VB1940 "all-in-one" cameras (FPGA versions 2507, 2510). Uses release-specific YAML manifests and board-type-specific program commands. Lattice and VB1940 commands must…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.