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.
curl -O https://raw.githubusercontent.com/zauberzeug/odrive-gui/main/CLAUDE.mdgit clone --depth 1 https://github.com/zauberzeug/odrive-guiWrote 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/instructions/zauberzeug/odrive-gui/claude-md)<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="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.1 | $0.00774 | $0.00774 |
| Opus 5 | $0.00387 | $0.00387 |
| Sonnet 5 | $0.00155 | $0.00155 |
| Haiku 4.5 | $0.00077 | $0.00077 |
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 7d 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.
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 on the event loop, so 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.
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.
- 7d ago First seen · 56 lines · 774 tokens per session scan A bf1dd1d7f97e
odrive-gui CLAUDE.md is an instructions file published in the GitHub repository zauberzeug/odrive-gui (47 stars, last pushed 12d ago), licensed MIT. It adds 774 tokens to every session, about $0.0039 per session on Opus 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.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.