usbtrace-module-authoring

Instructions for creating usbtrace modules, which extend a USB tracing tool with BPF code that observes system activity and user-space code that processes the results.

In plain words
What is it for?
Writing modules that observe and handle USB-related system events with BPF and user-space code.
Why use it?
It explains the required parts and approach for adding USB tracing functionality.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/dengtaowei/usbtrace/usbtrace-module-authoring
Clone the repo
git clone --depth 1 https://github.com/dengtaowei/usbtrace

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,035 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01035
Opus 5 $0.00000 $0.00517
Sonnet 5 $0.00000 $0.00207
Haiku 4.5 $0.00000 $0.00103

Measured yesterday against content hash 15697af0c49a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

usbtrace-module-authoring 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 yesterday.

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.

.cursor/rules/usbtrace-module-authoring.mdc · 93 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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.

  1. yesterday First seen · 93 lines · 0 tokens per session scan A 15697af0c49a

Subscribe to this mod's changes

usbtrace-module-authoring is a cursor rule published in the GitHub repository dengtaowei/usbtrace (2 stars, last pushed 12d ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 1,035 tokens. 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-31.