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 howdeploy/kisa-stack --skill wine-hid-device-toolsgit clone --depth 1 https://github.com/howdeploy/kisa-stackWrote 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/howdeploy/kisa-stack/wine-hid-device-tools)<a href="https://agentmods.dev/skills/howdeploy/kisa-stack/wine-hid-device-tools"><img src="https://agentmods.dev/badge/skills/howdeploy/kisa-stack/wine-hid-device-tools/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/howdeploy/kisa-stack/wine-hid-device-tools"><img src="https://agentmods.dev/badge/skills/howdeploy/kisa-stack/wine-hid-device-tools.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.00065 | $0.01656 |
| Opus 5.5 | $0.00026 | $0.00662 |
| Sonnet 5.5 | $0.00013 | $0.00331 |
| Haiku 4.5 | $0.00006 | $0.00166 |
Grade B, and why
wine-hid-device-tools 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 1mo 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.
sudo dmesg -wH | grep -Ei --line-buffered 'usb|hid|hidraw|keyboard|device' How it starts
The opening of the file, as written. The whole thing — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wine HID Device Tools
Hermes: все команды и скрипты этого скилла — обычный bash, запускай через
terminal. Вывод команд показывай пользователю как есть.
Goal
Help users run Windows keyboard and HID vendor tools on Linux when the device works as normal input but the configuration app cannot detect or control it. Diagnose Linux USB/HID visibility, hidraw permissions, the correct Wine prefix, and winebus settings before recommending a Windows VM.
Do not run Wine as root. Do not assume ~/.wine is the correct prefix.
Quick Workflow
- Confirm the device is wired over USB data, not only charging or still using Bluetooth/2.4 GHz.
- Find the device's VID/PID and
hidrawnodes. - Verify user access to the relevant
/dev/hidraw*nodes. - Generate and apply a udev rule if permissions are missing.
- Find the prefix that contains the installed vendor app.
- Apply
winebussettings to that exact prefix. - Relaunch the installed
.exewith careful shell quoting.
Use scripts first when available; they are read-only except for printing commands.
Discovery Scripts
List HID raw devices:
scripts/discover_hid_devices.sh
scripts/discover_hid_devices.sh 'aula|sonix|keyboard|0c45'
Find likely Wine prefixes and installed vendor executables:
scripts/find_wine_prefix_apps.sh
scripts/find_wine_prefix_apps.sh 'aula|akko|keychron|keyboard|driver'
Print setup commands for a known VID/PID:
scripts/print_hid_setup_commands.sh 0c45:800a
scripts/print_hid_setup_commands.sh 0c45:800a "/path/to/prefix"
The third script prints commands only. Review them with the user before applying sudo or registry changes.
Manual HID Checks
Use these when scripts are unavailable or more detail is needed:
lsusb
sudo dmesg -wH | grep -Ei --line-buffered 'usb|hid|hidraw|keyboard|device'
Inspect hidraw metadata:
for d in /sys/class/hidraw/hidraw*; do
[ -r "$d/device/uevent" ] || continue
echo "/dev/${d##*/}"
cat "$d/device/uevent"
echo
done
What ships with it
4 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.
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.
- 1mo ago First seen · 174 lines · 65 tokens per session scan B cc39c9979491
wine-hid-device-tools is a skill published in the GitHub repository howdeploy/kisa-stack (57 stars, last pushed 3d ago), licensed MIT. It adds 65 tokens to every session and 1,656 once invoked, about $0.0003 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.
Other skills, from other repositories
gke-ai-troubleshooting-tpu-dynamic-slices-monitoring
Monitors, troubleshoots, and manages GKE TPU Dynamic Slices custom resources. Use when checking TPU slice lifecycle states, troubleshooting slice provisioning failures, validating single-slice or multi-slice (JobSet) workload manifests, or safely patching stuck finalizers and disabling the slice controller. Don't use…
gke-ai-troubleshooting-tpu-vbar-oom
Diagnoses and prevents vbarcontrolagent segfaults, out-of-memory (OOM) errors, and TPU device initialization failures on TPU v6e nodes in GKE caused by race conditions during TPU device resets or high-frequency metrics polling. Use when troubleshooting vbarcontrolagent crashes, memory cgroup OOMs in serial console…
doca-flow
DOCA Flow packet steering on NVIDIA NICs/DPUs, linked into a C application: match/action pipes, ports, representors, forwarding, hairpin, counters. Trigger on packet steering, classifier, rule-matching, representor, hairpin or 5-tuple-to-queue questions even when "DOCA Flow" is not named. Also covers pipe validation…
competition-firmware-layout
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for firmware images, partition tables, boot chains, update packages, extracted filesystems, embedded configs, and device-facing trust boundaries. Use when the user asks to unpack firmware, map partition layout, inspect bootloader or init…
diagnose-driver-install
Diagnose NVIDIA driver installation failures on DeepOps-managed nodes — nvidia-smi errors, "No devices were found", DKMS build failures, or GPU pods crash-looping. Use before reinstalling anything.
catc-troubleshoot
Catalyst Center troubleshooting workflows - device unreachable investigation, client connectivity issues, interface down analysis, site-wide outage triage, wireless roaming problems, integration with pyATS for CLI-level diagnostics. Use when the device is managed by Catalyst Center and you want its…