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-updategit 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-update)<a href="https://agentmods.dev/skills/skyf0xx/pebble/pebble-update"><img src="https://agentmods.dev/badge/skills/skyf0xx/pebble/pebble-update/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/skyf0xx/pebble/pebble-update"><img src="https://agentmods.dev/badge/skills/skyf0xx/pebble/pebble-update.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.00021 | $0.00235 |
| Opus 5.5 | $0.00008 | $0.00094 |
| Sonnet 5.5 | $0.00004 | $0.00047 |
| Haiku 4.5 | $0.00002 | $0.00023 |
Grade A, and why
pebble-update 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 1mo 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.
What it actually says
Update Pebble
Updating Pebble is the same path as installing it — there is no separate
procedure. Follow the pebble:pebble-setup skill
(../pebble-setup/SKILL.md):
- Re-run its step 1 to pull the latest binary into
~/.hermes/bin/. - Re-run its step 2 to relaunch — on launch the binary reinstalls/updates
the embedded plugin into
~/.hermes/plugins/pebble/. - If the plugin changed,
hermes gateway restartso the agent picks it up.
No config migration is needed. See pebble-setup's Troubleshooting table if a
stale binary is suspected ("Replies show 'Running pebble_send…' instead of
rendering").
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.
- 1mo ago First seen · 22 lines · 21 tokens per session scan A 17e63e20e542
pebble-update is a skill published in the GitHub repository skyf0xx/Pebble (22 stars, last pushed 2mo ago), licensed MIT. It adds 21 tokens to every session and 235 once invoked, about $0.0001 per session on Opus 5.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
agile-web-product-agent
A Web product-planning helper that turns a tool request into a page list, key user flows, state rules, permission rules and a handover package. A state rule describes how something changes, such as from draft to published.
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-api-agent
A Web API design helper that turns page and data needs into a field dictionary, API rules, request and response formats, and a mock connection plan. An API is the agreed way that a front end exchanges data with a back end.
action-plan-assistant
A skill that turns a goal, meeting decision, or discussion into an action plan that can be used and shared.
daily-report-assistant
A skill that turns the day’s progress into a project status report that can be sent and followed up on.
message-summary-assistant
A single-agent assistant for shortening long emails or Chinese workplace messages from Feishu, WeCom, or DingTalk into structured summaries. The summaries are designed to be forwarded or shared without extra explanation.