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 commands/svitrix/svitrix-firmware/buildgit clone --depth 1 https://github.com/svitrix/svitrix-firmwareWrote 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/commands/svitrix/svitrix-firmware/build)<a href="https://agentmods.dev/commands/svitrix/svitrix-firmware/build"><img src="https://agentmods.dev/badge/commands/svitrix/svitrix-firmware/build.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 | $0.00012 | $0.00336 |
| Opus 5 | $0.00006 | $0.00168 |
| Sonnet 5 | $0.00002 | $0.00067 |
| Haiku 4.5 | $0.00001 | $0.00034 |
Grade A, and why
build 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 3d 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.
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.
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.
- 3d ago First seen · 46 lines · 12 tokens per session scan A a66c29135188
build is a command published in the GitHub repository svitrix/svitrix-firmware (31 stars, last pushed 1mo ago), with no licence file. It adds 12 tokens to every session and 336 once invoked, about $0.0001 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-09-01.
Other commands, from other repositories
code_review_asm_xtensa
Perform comprehensive manual review of Xtensa assembly code in FastLED ESP32 platforms for correctness, ABI compliance, safety, and performance.
scan
Discover Reolink devices on the local network (UDP broadcast, 2s).
devices
List registered Reolink aliases (from /.config/reolink-cli/aliases.toml).
aurora
Aurora - independent community smart home orchestrator. Routes any smart home request to the right specialist skill and recommends the correct Claude model. Use this as your starting point for Home Assistant, ESPHome, Node-RED, or any IoT automation task.
status
Reolink observability dashboard (fleet + gateway + monitor + cache + recent events).
rvcsi-nexmon
Nexmon CSI helpers — inspect a nexmoncsi .pcap, decode a Broadcom chanspec, or list the known Nexmon chips / Raspberry-Pi models.