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 agentmods add instructions/do4k/logitux/agents-mdgit clone --depth 1 https://github.com/do4k/LogiTuxWhat 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 | $0.01000 | $0.01000 |
| Opus 5 | $0.00500 | $0.00500 |
| Sonnet 5 | $0.00200 | $0.00200 |
| Haiku 4.5 | $0.00100 | $0.00100 |
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 2d 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`). 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
varwhenever the compiler allows it. Only fall back to an explicit type wherevaris illegal (e.g.[...]collection expressions,= nullinitializers) 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.Coreis BCL + P/Invoke only, no third-party libs; the UI layer (Avalonia, CommunityToolkit.Mvvm, Svg.*, SkiaSharp) stays inLogiTux.App. - Slider-driven hardware writes are debounced (see
DeviceCardViewModel.DebounceWriteAsync); reads must tolerate asleep devices (timeouts) and surface that via cardStatus, not exceptions. - Everything is verified against the real hardware before commit — run
dotnet run --project src/LogiTux.Pocand the app (webcam preview includes the--previewprobe for both MJPEG and forced-YUYV paths).
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.
- 2d ago First seen · 67 lines · 1,000 tokens per session scan B bdfbb7c8f5a8
LogiTux AGENTS.md is an instructions file published in the GitHub repository do4k/LogiTux (11 stars, last pushed 15d ago), licensed MIT. It adds 1,000 tokens to every session, about $0.0050 per session on Opus 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.
Other instructions, from other repositories
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.
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).
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.