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 varo6/reTerminal-sticky-skill --skill sticky-devicegit clone --depth 1 https://github.com/varo6/reTerminal-sticky-skillWrote 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/varo6/reterminal-sticky-skill/sticky-device)<a href="https://agentmods.dev/skills/varo6/reterminal-sticky-skill/sticky-device"><img src="https://agentmods.dev/badge/skills/varo6/reterminal-sticky-skill/sticky-device/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/varo6/reterminal-sticky-skill/sticky-device"><img src="https://agentmods.dev/badge/skills/varo6/reterminal-sticky-skill/sticky-device.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.00093 | $0.01012 |
| Opus 5 | $0.00046 | $0.00506 |
| Sonnet 5 | $0.00019 | $0.00202 |
| Haiku 4.5 | $0.00009 | $0.00101 |
Grade A, and why
sticky-device 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 11d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
reTerminal Sticky
Seeed Studio reTerminal Sticky: a magnetic ESP32-S3 e-ink note device. 3.97" 800x480 monochrome ePaper with 4-level grayscale, capacitive touch, 750 mAh battery.
Firmware is native ESP-IDF v5.4 / target esp32s3 (C/C++). ESPHome is the
supported no-C path. Apps are distributed by flashing whole firmware images — there
is no on-device app sandbox or multi-app runtime.
Read this first for any firmware task
Two rules cause most first-time failures on this device:
- Latch power on at boot. The device powers off unless firmware drives the
power-hold GPIOs within the first moments of
app_main(). See references/esp-idf-dev.md. - The panel is natively 800x480 landscape. Your logical canvas orientation is a choice you implement with a rotation in the pixel-write path. Pick one and keep touch coordinates in the same space. See references/display.md.
Where to look
| Task | File |
|---|---|
| Pin map, buses, part numbers, electrical/physical specs | references/hardware.md |
Toolchain, project skeleton, sdkconfig.defaults, build/flash, power latch, NVS, deep sleep |
references/esp-idf-dev.md |
| ePaper driver API, refresh modes, rotation, ghosting, partial-update strategy | references/display.md |
| Touch/GT911 gestures, buttons, IMU, SHT40, RTC, mic, buzzer, fuel gauge, SD | references/peripherals.md |
Publishing to Sticky Playground: integration.json, manifest, CI, review flow |
references/playground-registry.md |
| Existing firmware projects, ESPHome/Home Assistant, official docs, where the wiki is | references/ecosystem-and-docs.md |
Getting known-good driver sources
The registry holds a complete, buildable ESP-IDF app (sticky-2048) whose drivers are
the practical reference implementation for this board: seeed_epaper (SSD1677 panel),
gt911 (touch), bq27220 (fuel gauge), plus sticky_display / sticky_touch /
sticky_buzzer / sticky_ai_button wrappers.
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 79 lines · 93 tokens per session scan A 0a89ee2a17a6
sticky-device is a skill published in the GitHub repository varo6/reTerminal-sticky-skill (7 stars, last pushed 23d ago), licensed MIT. It adds 93 tokens to every session and 1,012 once invoked, about $0.0005 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-31.
Other skills, from other repositories
m5stack-cap-lora-1262
Hardware reference and firmware helper for the M5Stack Cap LoRa-1262 (SKU U214) — a snap-on cap for the Cardputer Adv (K132-Adv) and CardputerZero that carries a Semtech SX1262 sub-GHz LoRa radio (868–923 MHz, +22 dBm TX, external RP-SMA antenna) and an ATGM336H-6N GNSS receiver (GPS/QZSS/BeiDou/Galileo/GLONASS, UART…
new-device-skill
Build or update an M5Stack hardware skill in this marketplace — a Controller (a board that runs firmware, like Core2 or AtomS3), a Unit (a peripheral you drive from a Controller, like a ToF sensor or a relay), or a Chip (an Espressif SoC capability layer, like esp32-c6). Use whenever adding a new board/unit/chip to…
m5stack-tab5
Hardware reference and development helper for the M5Stack Tab5 (product code C145) — an ESP32-P4-based 5" touchscreen IoT/industrial terminal with an ESP32-C6 wireless co-processor, MIPI-DSI display, MIPI-CSI camera, ES8388 audio codec, BMI270 IMU, RX8130CE RTC, RS485, and a removable NP-F550 battery. Use this skill…
m5stack-core2
Hardware reference and development helper for the M5Stack Core2 family — a 2.0" touchscreen ESP32 (classic, Xtensa LX6) Controller built around an AXP192 power management IC, ILI9342C display, FT6336U capacitive touch, BM8563 RTC, and (on original/1.1/1.3 revisions) an MPU6886 or BMI270 IMU. Covers the plain Core2…
esp32-c6
Chip-level ESP-IDF capability reference for the ESP32-C6 SoC (single-core RISC-V HP core + RISC-V LP core, WiFi 6 + BLE 5.3 + Thread/Zigbee) — what the chip can do, distinct from any board's wiring. Use when a user wants to exploit ESP32-C6 hardware — WiFi 6/BLE/802.15.4 radio coexistence (Thread Border Router, Zigbee…
esp32-p4
Chip-level ESP-IDF capability reference for the ESP32-P4 SoC (dual-core RISC-V HP cores + a RISC-V LP core) — what the chip can do, distinct from any board's wiring. Use when a user wants to exploit ESP32-P4 hardware — MIPI-CSI/DSI with the on-chip ISP, hardware JPEG encode/decode, hardware H.264 encode, PPA/2D-DMA…