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/fastled/fastled/lintgit clone --depth 1 https://github.com/FastLED/FastLEDWhat 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.00007 | $0.00049 |
| Opus 5 | $0.00003 | $0.00024 |
| Sonnet 5 | $0.00001 | $0.00010 |
| Haiku 4.5 | $0.00001 | $0.00005 |
Grade A, and why
lint 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 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.
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.
What it actually says
Run linting and formatting checks across the codebase using bash lint.
Use the 'lint-agent' sub-agent to execute linting and report results in a clear, actionable format.
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 · 8 lines · 7 tokens per session scan A f383542c41da
lint is a command published in the GitHub repository FastLED/FastLED (7,479 stars, last pushed today), licensed MIT. It adds 7 tokens to every session and 49 once invoked, about $0.0000 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-08-30.
Other commands, from other repositories
cleanup
Land every unshipped set on main as its own patch release, then leave a clean tree.
hardware-specs
Read this before writing any code that touches peripherals, memory, Wi-Fi, camera, or audio. All GPIO and address numbers below are verified against the vendor BSP (ref/demo/ESP32-S3-CAM-OVxxxx/examples/ESP-IDF-v5.5.1/04dvpcameradisplay/components/waveshareesp32s3camovxxxx/include/bsp/esp32s3camovxxxx.h) and this…
review-firmware
Run embedded firmware code review (memory safety, ISR, RTOS, C/C++ UB).
monitor
Command "monitor" from chayuto/ws-ESP32-S3-CAM, covering read serial output from the board, fix 1 — stty -hupcl + dd (works reliably), fix 2 — pyserial but set dtr/rts before open, optional: pulse rts only to reset without touching dtr and healthy read (once the dtr trap is avoided).
peripherals
Use the vendor BSP waveshare/esp32s3camovxxxx for anything nontrivial. It hides the CH32V003 IO-expander quirks, I²C bus init, camera pin config, and codec addresses. Header: ref/demo/ESP32-S3-CAM-OVxxxx/examples/ESP-IDF-v5.5.1/04dvpcameradisplay/components/waveshareesp32s3camovxxxx/include/bsp/esp32s3camovxxxx.h.
power-budget
Calculate power budget for the current embedded project.