What is LogiTux AGENTS.md?

Project instructions for LogiTux, a .NET and Avalonia alternative to Logitech G HUB that communicates directly with devices such as mice, headsets, lights, and webcams. They describe the source layout, hardware access, UI, and verification rules.

Use them when developing device drivers, HID++ communication, webcam and lighting controls, the Avalonia dashboard, the hardware probe, installation files, or build and verification tasks.

They help agents make changes in the correct project areas while respecting the hardware, framework, and build conventions.

How do4k/LogiTux configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to do4k/LogiTux. 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/do4k/LogiTux/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/do4k/LogiTux

Made for: Codex, OpenCode.

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/do4k/logitux/agents-md/github.svg)](https://agentmods.dev/instructions/do4k/logitux/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/do4k/logitux/agents-md"><img src="https://agentmods.dev/badge/instructions/do4k/logitux/agents-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/do4k/logitux/agents-md"><img src="https://agentmods.dev/badge/instructions/do4k/logitux/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,000 This file is loaded in full into every session.

When invoked 1,000 The same file — it is already loaded in full.

Security scan B 1 finding. 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.01000	$0.01000
Opus 5.5	$0.00400	$0.00400
Sonnet 5.5	$0.00200	$0.00200
Haiku 4.5	$0.00100	$0.00100

Measured 2mo ago against content hash bdfbb7c8f5a8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade B, and why

LogiTux AGENTS.md scanned grade B 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 2mo 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.

rule (`~/.local/bin`, plus sudo for `/etc/udev/rules.d`).

AGENTS.md · 67 lines

How it starts

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

AGENTS.md

LogiTux — a Logitech G HUB alternative, with hardware talked to directly (hidraw, V4L2): no cgo, no libhidapi, no libv4l. Implemented as a . NET/Avalonia solution that replaced the repo's original Go/Fyne implementation entirely (source layout at the repo root since then).

Repo layout

src/LogiTux.Core — the hardware library: hidraw device I/O, the HID++ transport (feature calls, notifications), the device drivers (G Pro mouse, PRO X wireless headset, Litra lights, UVC webcams), V4L2 controls and capture streaming. BCL + P/Invoke only, zero third-party libs. Namespaces mirror the Go lineage (Devices/Mouse/GProMouse.cs, Hidpp/HidppConn.cs, V4l2/V4l2Device.cs).
src/LogiTux.App — the Avalonia UI (CommunityToolkit.Mvvm, Svg.Controls.Skia.Avalonia, SkiaSharp): dark G HUB-style dashboard with one card per device, G HUB-mirroring section pages (Sensitivity, Assignments, Lighting, Sound, Camera/Image tabs), and a live 640x480 webcam preview at ~15 fps.
src/LogiTux.Poc — console probe for hardware iterations (dotnet run --project src/LogiTux.Poc -- --only=/dev/video0 --preview [-yuyv], --set-rgb=, --set-sidetone=, --set-eq=).
install/, packaging/, .github/ — udev rule + .desktop entry, nfpm .deb config / macOS Info.plist / CI (Linux binary + .deb, Windows .exe, macOS .app, tag releases).

C# conventions (src/)

Use var whenever the compiler allows it. Only fall back to an explicit type where var is illegal (e.g. [...] collection expressions, = null initializers) or where a deconstruction needs its element names.
One model/type per class file, named after the type. No multi-type files — records, enums and small helpers each get their own file.
XML doc comments use block form: /// <summary> on its own line, body, then /// </summary> on its own line (and likewise for <param>/<returns> where used).
Prepend comments with Ported from internal/... where the Go lineage matters (protocol constants, ioctl layouts, timer periods still follow Go's numbers — trust them over recollection).
Device I/O in LogiTux.Core is BCL + P/Invoke only, no third-party libs; the UI layer (Avalonia, CommunityToolkit.Mvvm, Svg.*, SkiaSharp) stays in LogiTux.App.
Slider-driven hardware writes are debounced (see DeviceCardViewModel.DebounceWriteAsync); reads must tolerate asleep devices (timeouts) and surface that via card Status, not exceptions.
Everything is verified against the real hardware before commit — run dotnet run --project src/LogiTux.Poc and the app (webcam preview includes the --preview probe for both MJPEG and forced-YUYV paths).

Read the full file on GitHub · 67 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.

2mo ago First seen · 67 lines · 1,000 tokens per session scan B bdfbb7c8f5a8

Subscribe to this mod's changes

LogiTux AGENTS.md is an instructions file published in the GitHub repository do4k/LogiTux (11 stars, last pushed 2mo ago), licensed MIT. It adds 1,000 tokens to every session, about $0.0040 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

C# and .NET Hardware and IoT Languages

LogiTux AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
LogiTux AGENTS.mddo4k/LogiTux	Instructions file	11	2mo ago	MIT	B	1,000	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

LogiTux: Instructions file for Codex