Skip to content
Back to search

backlit

MarketplaceWorks with Claude CodeGitHub

ASUS TUF keyboard lighting that follows Claude Code.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/sujatx--backlit-for-claude/badge.svg)](/listings/sujatx--backlit-for-claude)

HTML

<a href="/listings/sujatx--backlit-for-claude"><img src="/api/listings/sujatx--backlit-for-claude/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

In a terminal session:

/plugin install backlit --marketplace Sujatx/backlit-for-claude

Or from a shell:

claude plugin install backlit --marketplace Sujatx/backlit-for-claude

In the desktop app, where `/plugin` does not run: click **+** next to the prompt box, then **Plugins**, **Add marketplace** with `Sujatx/backlit-for-claude`, then **Add plugin**.

Choose the **user** scope to have it in every session.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 6 lines
  1. {
  2. "name": "backlit",
  3. "owner": { "name": "Sujatx" },
  4. "description": "ASUS TUF keyboard lighting that follows Claude Code.",
  5. "plugins": [{ "name": "backlit", "source": "./" }]
  6. }
README.md · README · 101 lines
  1. # backlit-for-claude
  2. Your ASUS TUF keyboard lights follow what Claude Code is doing.
  3. | Claude Code is... | Keyboard |
  4. |---|---|
  5. | working | orange, breathing |
  6. | waiting for you (permission, question) | red |
  7. | done with its answer | green for 30 s |
  8. | idle | colour cycle |
  9. | hit an error or refusal | red |
  10. It is a [Claude Code](https://claude.com/claude-code) mod: a few hooks plus a tiny Rust helper (`kbl.exe`) that sets the lighting. It uses no tokens, adds nothing to the model's context, and needs no admin rights.
  11. ## Tested on
  12. | Laptop | BIOS | Result |
  13. |---|---|---|
  14. | ASUS TUF Gaming A15 FA506NCG (Windows 11) | FA506NCG.306 | Works: static, breathe and colour cycle |
  15. Other TUF laptops that G-Helper drives the same way may work. They are untried; see Contributing.
  16. ## Install
  17. In a terminal session:
  18. ```
  19. /plugin install backlit --marketplace Sujatx/backlit-for-claude
  20. ```
  21. Or from a shell:
  22. ```
  23. claude plugin install backlit --marketplace Sujatx/backlit-for-claude
  24. ```
  25. In the desktop app, where `/plugin` does not run: click **+** next to the prompt box, then **Plugins**, **Add marketplace** with `Sujatx/backlit-for-claude`, then **Add plugin**.
  26. Choose the **user** scope to have it in every session.
  27. ## What it does to your laptop
  28. `kbl.exe` opens the ASUS ACPI device (`\\.\ATKACPI`) and sends the same lighting commands [G-Helper](https://github.com/seerge/g-helper) sends: a colour and an effect for the keyboard. It never changes brightness, so your Fn-key level stays. This is an undocumented firmware interface, used at your own risk. Whether a setting survives sleep or a reboot has not been checked.
  29. ## Customise
  30. - Colours and effects: edit the `state` table in `helper/src/main.rs` and rebuild (below). Modes are `0` static, `1` breathe, `2` colour cycle.
  31. - Time green stays: `IDLE_AFTER_DONE_MS` in `hooks/register.ts`.
  32. - Try a setting by hand: `bin\kbl.exe rgb <mode> <r> <g> <b> <speed>`.
  33. ## Build the helper yourself
  34. The repo ships a prebuilt `bin/kbl.exe`. Check it, or replace it with your own build:
  35. ```
  36. cd helper
  37. cargo build --release
  38. copy target\release\kbl.exe ..\bin\kbl.exe
  39. ```
  40. SHA-256 of the shipped `bin/kbl.exe` (v0.1.1):
  41. ```
  42. e52e55f787847f9fcaae63ef33a7b9aec35dcd4c177a4a6c477feeb2d0d8b49a
  43. ```
  44. A rebuild may differ byte for byte, because Rust embeds paths and build details.
  45. ## Layout
  46. ```
  47. .claude-plugin/ plugin and marketplace manifests
  48. hooks/ the mod (register.ts) and its test
  49. helper/ Rust source for kbl.exe
  50. bin/ prebuilt kbl.exe
  51. ```
  52. Run the test with `claude plugin test .`.
  53. ## Limits
  54. - Several Claude Code sessions at once share one keyboard, so the last event wins.
  55. - Windows only.
  56. ## Contributing
  57. Help for other devices is very welcome. The most useful thing is a test report:
  58. 1. Install the mod, or just run `bin\kbl.exe rgb 0 255 0 0 0` (static red) in a terminal.
  59. 2. Open an issue with your laptop model, BIOS version (`Get-CimInstance Win32_BIOS`) and what happened to the keyboard, plus the `rgb=` number the command prints (`1` means the firmware accepted it).
  60. 3. Try modes `1` (breathe) and `2` (colour cycle) and tell us whether they matched.
  61. I'll add working models to the table above. Pull requests are welcome too: support for other ASUS models or endpoints, per-key or multi-zone keyboards, other operating systems, other colours or states. Keep changes small, run `claude plugin test .` and say which hardware you tried it on. Please don't send untested firmware writes: stick to the documented G-Helper commands, and never use BIOS-persistent ones.
  62. ## Credits
  63. The ACPI device path, request framing, device IDs and effect modes come from [G-Helper](https://github.com/seerge/g-helper) by seerge (`app/AsusACPI.cs`, GPL-3.0). This project reimplements that interface in Rust and does not include G-Helper's code. Thanks to the G-Helper authors and community.
  64. ## License
  65. [MIT](LICENSE)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.