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 easyzoom/aix-skills --skill lvgl-integrationgit clone --depth 1 https://github.com/easyzoom/aix-skillsWrote 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/easyzoom/aix-skills/lvgl-integration)<a href="https://agentmods.dev/skills/easyzoom/aix-skills/lvgl-integration"><img src="https://agentmods.dev/badge/skills/easyzoom/aix-skills/lvgl-integration/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/easyzoom/aix-skills/lvgl-integration"><img src="https://agentmods.dev/badge/skills/easyzoom/aix-skills/lvgl-integration.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.00038 | $0.00647 |
| Opus 5 | $0.00019 | $0.00324 |
| Sonnet 5 | $0.00008 | $0.00129 |
| Haiku 4.5 | $0.00004 | $0.00065 |
Grade A, and why
lvgl-integration 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LVGL Integration
Overview
Use this skill to integrate LVGL by proving four porting contracts: display flush, input device read, tick/timebase, and memory/draw buffer configuration. UI bugs often come from driver timing or buffer ownership, not widget logic.
When To Use
Use this skill when:
- The user wants to add or debug LVGL/littlevGL on an MCU or embedded Linux display.
- The issue involves blank screen, wrong colors, tearing, touch offset, slow refresh, memory faults, tick handling, or display flush callbacks.
- The project has display, touch, encoder, keypad, RTOS, or DMA/cache constraints.
Do not use this skill when the display hardware has no proven signal. Use hardware-interface-debug first.
First Questions
Ask for:
- LVGL major version and target platform.
- Display controller, resolution, color format, interface, and framebuffer/draw buffer strategy.
- Input devices: touch, buttons, encoder, keypad, or none.
- Tick source and
lv_timer_handlerscheduling. - RAM budget, heap policy, RTOS use, DMA/cache involvement.
- Current symptom and minimal screen test result.
Integration Checklist
-
Bring up display flush. Fill the screen with solid colors before creating complex widgets.
-
Configure draw buffers. Buffer size, color format, stride, and cache/DMA policy must match the display path.
-
Provide a reliable tick. LVGL needs a monotonic tick and regular handler execution.
-
Add input after display. Touch/encoder/keypad should be calibrated and tested independently.
-
Bound memory. Configure heap, widget count, image assets, fonts, and buffers for the target RAM.
-
Verify refresh performance. Measure frame time, flush completion, and whether
lv_disp_flush_readyis called correctly.
Common Failures
- Blank screen because flush callback never calls ready.
- Wrong colors from RGB/BGR or 16-bit endian mismatch.
- Touch coordinates need rotation/calibration transform.
- UI freezes because
lv_timer_handleris not called regularly. - DMA reads stale cache lines or writes to non-DMA-capable memory.
- Fonts/images exceed flash or RAM budgets.
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.
- 10d ago First seen · 84 lines · 38 tokens per session scan A 4b7190144b60
lvgl-integration is a skill published in the GitHub repository easyzoom/aix-skills (31 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 647 once invoked, about $0.0002 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 skills, from other repositories
container-home
Answer questions, assist with planning, and help with design decisions for Mick's off-grid shipping container lake home project. Trigger when the user mentions the container home, lake home, Stewart County, LBL, the expansion, solar system, septic permitting, or retirement property.
eide
A build tool for EIDE projects, an embedded-development extension for Visual Studio Code. It finds EIDE project settings and builds firmware using ARM CC or GCC.
audit
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
workflow
A workflow skill for embedded-device projects that plans and runs building, flashing, debugging, observing, and diagnosis tasks.
investigate
Investigate bugs and errors in Elixir/Phoenix — root-cause analysis for crashes, exceptions, stack traces, test failures. Use --parallel for deep 4-track investigation.
narrow-bare-rescue
Narrow bare rescue in Elixir so real errors like KeyError and typos propagate instead of being swallowed. Use to audit rescues and refactor error handling.