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 skyf0xx/Pebble --skill pebble-protocol-uigit clone --depth 1 https://github.com/skyf0xx/PebbleWrote 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/skyf0xx/pebble/pebble-protocol-ui)<a href="https://agentmods.dev/skills/skyf0xx/pebble/pebble-protocol-ui"><img src="https://agentmods.dev/badge/skills/skyf0xx/pebble/pebble-protocol-ui.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00058 | $0.02733 |
| Opus 5 | $0.00029 | $0.01367 |
| Sonnet 5 | $0.00012 | $0.00547 |
| Haiku 4.5 | $0.00006 | $0.00273 |
Grade A, and why
pebble-protocol-ui 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 8d 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pebble UI component catalogue (OpenUI Lang)
Reference for building pebble_send type "ui" blocks. The protocol itself
(message/ui/status/push, the ui_action round-trip) lives in
pebble:pebble-protocol — view that first if you haven't.
A ui block's spec field is a string of OpenUI Lang
— a compact, declarative UI language. Pebble renders it with @openuidev's
built-in component library (openuiLibrary), whose registered entry component
is Stack (so every program starts root = Stack(...)).
Syntax rules (read this first)
- Each statement is on its own line:
identifier = Expression rootis the entry point — every program must defineroot = Stack(...). Ifrootis missing, nothing renders.- Expressions: strings (
"..."), numbers, booleans,null, arrays ([...]), objects ({...}), component callsTypeName(arg1, arg2, ...), built-in calls@Name(args), member access (data.rows.title), ternaries ($show ? a : b), and binary ops ("" + $n + " days"). - Define a reference on one line, use it later:
title = TextContent("Hi"). Forward references are allowed —root = Stack([chart])can appear beforechart = ...(hoisting). Generate top-down: layout → components → data, so the shell streams in first. - Arguments are POSITIONAL — order matters, names don't (they map to props
by the component's schema key order). Write
Stack([kids], "row", "l"), notStack([kids], direction: "row"). Colon/named syntax silently breaks. Omit trailing optional args to skip them; passnullto skip a middle one (e.g.Button("Go", null, "primary")). - Strings use double quotes with backslash escaping.
- Your entire
specis Lang — no markdown fences, no prose, just statements.
The interaction model
Interactivity comes from buttons, forms, and optional reactive state
($variables). Two kinds of outcome:
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.
- 8d ago First seen · 194 lines · 58 tokens per session scan A 54cb997c15a9
pebble-protocol-ui is a skill published in the GitHub repository skyf0xx/Pebble (22 stars, last pushed 1mo ago), licensed MIT. It adds 58 tokens to every session and 2,733 once invoked, about $0.0003 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
animated-portfolio-sites
Build a one-page animated personal or portfolio site (canvas starfield, rotating galaxies with mouse parallax, hidden accordion/card content, anchor nav) and publish it free on GitHub Pages. Covers the canvas technique and the Pages permission wall, not just one task.
agile-web-builder-agent
A Web front-end planning helper that turns product handover materials into a project structure, suggested page files, components, screen states and a first coding task list.
agile-web-qa-agent
A Web prototype acceptance helper that checks whether the prototype contains the minimum information needed to start development. It produces page-by-page acceptance checks, risks and missing pieces.
wechat-mini-program-solo-assistant
A Chinese-language skill for turning WeChat Mini Program requests into a code skeleton and implementation package. WeChat Mini Programs are small applications that run inside WeChat.
agile-web-development-solo-assistant
A single-agent assistant that turns web-tool requirements into a page structure ready for development, an interface outline, and a code skeleton.
wechat-mini-program-builder-agent
A guide for planning front-end implementations from a page or feature structure. It suggests an implementation order, components, and a basic page layout.