What is odrive-gui CLAUDE.md?

Project instructions for a NiceGUI web app that discovers ODrive motor controllers connected by USB and shows a live control panel for each one.

They help agents change the controls, run the app with real or simulated ODrive hardware, and run its tests, lint checks, and type checks.

They explain how the app is organised and how to run and test it, including when no physical motor controller is available.

How zauberzeug/odrive-gui configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to zauberzeug/odrive-gui. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/zauberzeug/odrive-gui/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/zauberzeug/odrive-gui

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/zauberzeug/odrive-gui/claude-md/github.svg)](https://agentmods.dev/instructions/zauberzeug/odrive-gui/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/zauberzeug/odrive-gui/claude-md"><img src="https://agentmods.dev/badge/instructions/zauberzeug/odrive-gui/claude-md/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/zauberzeug/odrive-gui/claude-md"><img src="https://agentmods.dev/badge/instructions/zauberzeug/odrive-gui/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 828 This file is loaded in full into every session.

When invoked 828 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00828	$0.00828
Opus 5.5	$0.00331	$0.00331
Sonnet 5.5	$0.00166	$0.00166
Haiku 4.5	$0.00083	$0.00083

Measured 12d ago against content hash 0bbe6295b92a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

odrive-gui CLAUDE.md scanned grade A with 0 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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

CLAUDE.md · 56 lines

How it starts

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

ODrive GUI — agent guide

A small NiceGUI web app to tune and debug ODrive motor controllers. It discovers ODrives on the USB bus and renders one live control panel per device.

Layout

Path	What
`src/main.py`	Entry point: USB discovery loop + the page. `python src/main.py`.
`src/controls.py`	The per-device control panel — `controls(odrv)`. All the UI lives here.
`src/theme.py`	Shared colour scheme, default props + dark mode (`apply_theme()`), used by the app and the mock runner.
`tools/mock_odrive.py`	A faithful in-memory fake ODrive + a stub of the `odrive` package (incl. its discovery API). Lets the UI run, be screenshotted and tested with no hardware attached.
`tools/run_mock.py`	`python tools/run_mock.py [port]` — runs the real `main.py` with one mock device plugged in.
`tests/`	pytest tests driving the mock through NiceGUI's `User` fixture: the panel (`test_render.py`) and the real `main.py` incl. hot-plugging (`test_main.py`).

Run it

uv sync

uv run python src/main.py            # needs a real ODrive on USB
uv run python tools/run_mock.py      # no hardware — opens on :8113

Test / lint / type-check (the CI gates)

uv run ruff check . && uv run ruff format --check .
uv run mypy src
uv run pytest

Note: pytest runs against the odrive stub (tests/conftest.py), so a green suite says nothing about the real odrive import. CI's separate boot job is what verifies src/main.py actually starts against the locked dependency set, and its docker job that the published image does too.

How the device object works (important)

controls(odrv) takes a live fibre remote object, so it is dynamically typed (Any). Every attribute it reads (odrv.axis0.motor.current_control.Iq_measured, odrv.axis0.controller.config.pos_gain, …) mirrors the ODrive 0.5.x/0.6.x object tree. Every property read is a blocking USB round-trip, so after the panel is built all device traffic goes through the single _usb worker in controls.py (_Mirror for bound values, _on_usb for timer reads, _send for writes and commands) — never read or write the device on the event loop, and keep timers lean. When you change the UI, mirror the same attribute path in tools/mock_odrive.py so the hardware-free tests keep covering it.

Read the full file on GitHub · 56 lines

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.

12d ago Changed · +54 tokens per session 0bbe6295b92a
2mo ago First seen · 56 lines · 774 tokens per session scan A bf1dd1d7f97e

Subscribe to this mod's changes

odrive-gui CLAUDE.md is an instructions file published in the GitHub repository zauberzeug/odrive-gui (49 stars, last pushed 11d ago), licensed MIT. It adds 828 tokens to every session, about $0.0033 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Hardware and IoT

odrive-gui CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
odrive-gui CLAUDE.mdzauberzeug/odrive-gui	Instructions file	49	11d ago	MIT	A	828	Claude Code
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	9,719	GitHub Copilot
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	5,516	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	today	MIT	A	4,680	Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	3,093	GitHub Copilot
vscode model-prompts.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	2,022	GitHub Copilot

odrive-gui: Instructions file for Claude Code