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 instructions/deyloop/lianli_207_lcd/agents-mdgit clone --depth 1 https://github.com/deyloop/lianli_207_lcdWrote 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/instructions/deyloop/lianli_207_lcd/agents-md)<a href="https://agentmods.dev/instructions/deyloop/lianli_207_lcd/agents-md"><img src="https://agentmods.dev/badge/instructions/deyloop/lianli_207_lcd/agents-md.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.1 | $0.01438 | $0.01438 |
| Opus 5 | $0.00719 | $0.00719 |
| Sonnet 5 | $0.00288 | $0.00288 |
| Haiku 4.5 | $0.00144 | $0.00144 |
Grade B, and why
lianli_207_lcd AGENTS.md scanned grade B with 2 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 5d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo ./install.sh /path/to/background.jpg Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
out = subprocess.check_output(["nvidia-smi", ...], timeout=2).decode().strip() How it starts
The opening of the file, as written. The whole thing — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md - Lian Li Lancool 207 LCD Driver
Project Overview
Linux driver for the Lian Li Lancool 207 Digital LCD screen. This Python 3.12+ project communicates with the LCD via USB, renders system stats (CPU/GPU/RAM/Network), and pushes images to the display.
Build Commands
Installation
# Using uv (recommended)
uv sync
# Using pip
pip install -e .
System Installation (requires root)
# Install with systemd service (requires background image path)
sudo ./install.sh /path/to/background.jpg
# Reinstall/reload after changes
sudo ./reinstall.sh
# Uninstall completely
sudo ./uninstall.sh
# Check service status
journalctl -u lcd-driver -f
Running the driver (development)
lcd-driver <background_image>
Type checking (only tool configured)
# Run basedpyright
basedpyright lcd_driver/
# Or using pyright directly if installed
pyright lcd_driver/
Building the package
python -m build
Running a single test
No tests exist yet. To add tests, use pytest:
pytest tests/ # Run all tests
pytest tests/test_file.py # Run specific test file
pytest tests/test_file.py::test_function_name # Run specific test
Code Style Guidelines
General
- Python 3.12+ required
- Follow PEP 8 with 100 character line limit
- Use type hints for all function signatures and variables when beneficial
- Run
basedpyrightbefore committing - it must pass without errors
Imports
- Standard library imports first
- Third-party imports second
- Local imports last
- Use absolute imports (e.g.,
from lcd_driver import foo) - Separate import groups with a single blank line
# Correct
import os
import sys
import struct
import time
import usb.core
import usb.util
from PIL import Image, ImageDraw, ImageFont
from lcd_driver import utils
Naming Conventions
- Use
snake_casefor functions, variables, and methods - Use
SCREAMING_SNAKE_CASEfor constants - Use
PascalCasefor classes - Use descriptive names - avoid single letters except in tight loops
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.
- 5d ago First seen · 207 lines · 1,438 tokens per session scan B fc4410daca91
lianli_207_lcd AGENTS.md is an instructions file published in the GitHub repository deyloop/lianli_207_lcd (2 stars, last pushed 3mo ago), licensed MIT. It adds 1,438 tokens to every session, about $0.0072 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
cml-mcp AGENTS.md
AGENTS.md instructions for xorrkaz/cml-mcp, covering agents.md — cml mcp server, project overview, compatibility goal, repository layout and tool modules (src/cmlmcp/tools/).
brilliant_sdk AGENTS.md
Instructions for brilliantlabsAR/brilliant_sdk, covering brilliant sdk — agent guide, how an app works (the pattern behind everything), minimal reading paths, verify without hardware and testing.
NeoMind CLAUDE.md
Claude Code instructions for camthink-ai/NeoMind, covering neomind — edge ai platform for iot, development commands, ecosystem repositories, extension package contract (.nep) and device type template contract (json).
cad-cae-copilot copilot-instructions.md
Copilot instructions for armpro24-blip/cad-cae-copilot, covering github copilot — aieng workspace and essentials.
phone-mcp CLAUDE.md
Claude Code instructions for premex-ab/phone-mcp, covering claude.md, project overview, build commands, architecture and module layout.
zmk-config AGENTS.md
AGENTS.md instructions for urob/zmk-config, covering customization guide, ground rules, how the multi-board layout works, adding a new board and where to change what.