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 dakshaymehta/cardputer-claude-os --skill m5-onboardgit clone --depth 1 https://github.com/dakshaymehta/cardputer-claude-osWrote 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/dakshaymehta/cardputer-claude-os/m5-onboard)<a href="https://agentmods.dev/skills/dakshaymehta/cardputer-claude-os/m5-onboard"><img src="https://agentmods.dev/badge/skills/dakshaymehta/cardputer-claude-os/m5-onboard/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/dakshaymehta/cardputer-claude-os/m5-onboard"><img src="https://agentmods.dev/badge/skills/dakshaymehta/cardputer-claude-os/m5-onboard.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.00283 | $0.06360 |
| Opus 5 | $0.00142 | $0.03180 |
| Sonnet 5 | $0.00057 | $0.01272 |
| Haiku 4.5 | $0.00028 | $0.00636 |
Grade B, and why
m5-onboard scanned grade B 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 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- **Linux** — `sudo apt-get install -y git` / `sudo dnf install -y git` / `sudo pacman -S --noconfirm git`. Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **macOS** — Python 3 is usually pre-installed as `/usr/bin/python3` on any current macOS (shipped by Apple). If for some reason it isn't, `brew install [email protected]` via Homebrew is the go-to; if Homebrew itself is miss This is a copy
89% identical to m5-onboard — 47 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
M5Stack Onboarding
This skill automates the full cold-start workflow for an M5Stack ESP32 device: detect on USB, identify model, flash UIFlow 2.0, and push a MicroPython app bundle onto /flash/ so the device boots into user software. The apps we ship (Claude Buddy, Snake, Hello) talk over BLE or USB. The workflow runs on macOS, Linux, and Windows; the skill was developed against an M5Stack Basic v2.6 (CH9102 bridge, ESP32-D0WDQ6-V3, 16 MB flash) and generalized to cover the rest of the Core family, with the Cardputer-Adv (ESP32-S3, native USB) as the current default target.
Installation (one-time, per machine)
The skill lives at .claude/skills/m5-onboard/ inside this repo, so Claude Code auto-discovers it whenever the repo is added as a plugin (or the repo is opened as the working directory and .claude/skills/ is on the discovery path). No symlink step is needed in the normal case — clone the repo, point Claude Code at it, and the skill is live.
git clone <m5stack repo> # anywhere — clone location doesn't matter
The buddy/ sibling directory ships in the same repo, so --apps buddy works out of the box after a single clone — the skill resolves the bundle relative to its own install location (via os.path.realpath(__file__)), so the repo can live anywhere on disk. ~/Downloads/m5stack/buddy/device and ~/Desktop/m5stack/buddy/device are checked as conventional fallbacks if the script-relative path doesn't pan out. Set M5_BUDDY_DIR only if you want to point at a different bundle than the one bundled with this clone — see the Platform notes section.
When to use
Use this when a user plugs in an M5Stack device and wants it provisioned. The decision tree:
- Fresh/unknown device → run
onboard.py --apps buddyend-to-end (detect → identify → flash → install apps). This is the default path. - Already-flashed device, user just wants apps installed/refreshed → run
install_apps.py --src buddy(or any--src <path>to a directory of.pyfiles). - Flashed device, something feels broken → run
smoke_test.py(I2C + LCD + speaker + button check). - User wants to know what's on the bus / what the device can do →
smoke_test.py.
What ships with it
48 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.
- references/hardware_signatures.md 3.4 KB
- references/uiflow2_nvs.md 2.7 KB
- scripts/detect.py 7.0 KB runs code
- scripts/fetch_firmware.py 15 KB runs code
- scripts/flash.py 8.8 KB runs code
- scripts/install_apps.py 20 KB runs code
- scripts/mpy_repl.py 6.4 KB runs code
- scripts/onboard.py 48 KB runs code
- scripts/smoke_test.py 2.0 KB runs code
- scripts/vendor_path.py 2.7 KB runs code
- scripts/vendor/__init__.py 2.1 KB runs code
- scripts/vendor/pyserial-3.5.dist-info/DESCRIPTION.rst 320 B
- scripts/vendor/pyserial-3.5.dist-info/entry_points.txt 112 B
- scripts/vendor/pyserial-3.5.dist-info/INSTALLER 4 B
- scripts/vendor/pyserial-3.5.dist-info/METADATA 1.6 KB
- scripts/vendor/pyserial-3.5.dist-info/metadata.json 1.6 KB
- scripts/vendor/pyserial-3.5.dist-info/RECORD 4.7 KB
- scripts/vendor/pyserial-3.5.dist-info/REQUESTED 0 B
- scripts/vendor/pyserial-3.5.dist-info/top_level.txt 7 B
- scripts/vendor/pyserial-3.5.dist-info/WHEEL 110 B
- scripts/vendor/serial/__init__.py 3.1 KB runs code
- scripts/vendor/serial/__main__.py 45 B runs code
- scripts/vendor/serial/rfc2217.py 58 KB runs code
- scripts/vendor/serial/rs485.py 3.2 KB runs code
- scripts/vendor/serial/serialcli.py 9.0 KB runs code
- scripts/vendor/serial/serialjava.py 8.3 KB runs code
- scripts/vendor/serial/serialposix.py 34 KB runs code
- scripts/vendor/serial/serialutil.py 21 KB runs code
- scripts/vendor/serial/serialwin32.py 20 KB runs code
- scripts/vendor/serial/threaded/__init__.py 9.1 KB runs code
- scripts/vendor/serial/tools/__init__.py 0 B runs code
- scripts/vendor/serial/tools/hexlify_codec.py 3.6 KB runs code
- scripts/vendor/serial/tools/list_ports_common.py 3.6 KB runs code
- scripts/vendor/serial/tools/list_ports_linux.py 4.4 KB runs code
- scripts/vendor/serial/tools/list_ports_osx.py 11 KB runs code
- scripts/vendor/serial/tools/list_ports_posix.py 4.4 KB runs code
- scripts/vendor/serial/tools/list_ports_windows.py 16 KB runs code
- scripts/vendor/serial/tools/list_ports.py 3.3 KB runs code
- scripts/vendor/serial/tools/miniterm.py 37 KB runs code
- scripts/vendor/serial/urlhandler/__init__.py 0 B runs code
- scripts/vendor/serial/urlhandler/protocol_alt.py 2.0 KB runs code
- scripts/vendor/serial/urlhandler/protocol_cp2110.py 8.3 KB runs code
- scripts/vendor/serial/urlhandler/protocol_hwgrep.py 3.1 KB runs code
- scripts/vendor/serial/urlhandler/protocol_loop.py 10 KB runs code
- scripts/vendor/serial/urlhandler/protocol_rfc2217.py 317 B runs code
- scripts/vendor/serial/urlhandler/protocol_socket.py 14 KB runs code
- scripts/vendor/serial/urlhandler/protocol_spy.py 8.9 KB runs code
- scripts/vendor/serial/win32.py 11 KB runs code
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 · 195 lines · 283 tokens per session scan B 82a12cde504e
m5-onboard is a skill published in the GitHub repository dakshaymehta/cardputer-claude-os (202 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 283 tokens to every session and 6,360 once invoked, about $0.0014 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, makes network calls). It is 89% identical to m5-onboard, differing in 47 lines, and is treated as a copy.
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.