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 commands/openclaw/peekaboo/daemongit clone --depth 1 https://github.com/openclaw/PeekabooWhat 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 | $0.00000 | $0.00921 |
| Opus 5 | $0.00000 | $0.00461 |
| Sonnet 5 | $0.00000 | $0.00184 |
| Haiku 4.5 | $0.00000 | $0.00092 |
Grade A, and why
daemon 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 2d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
peekaboo daemon
Manage the on-demand headless daemon that keeps Peekaboo state warm, tracks windows live, and serves bridge requests.
The default listener is ~/Library/Application Support/Peekaboo/daemon.sock, separate from Peekaboo.app's
bridge.sock.
After upgrading from a version that used bridge.sock for the daemon, default status, start, and stop
commands detect that legacy daemon by its daemon status. Peekaboo.app is never treated as a daemon.
Normal automation commands migrate legacy auto or manual daemons that advertise atomic conditional stop. The daemon
keeps its prior lifecycle mode, poll interval, and auto idle timeout, so a manually started daemon remains manual after
migration. MCP sessions remain process-owned and are never migrated.
When bridge.sock belongs to a healthy Peekaboo.app GUI host instead, commands outside the exact-build preference keep
using that app-held TCC context and start the reusable daemon only if the app host is unavailable or lacks the required
capability. Implicit commands that require screen capture, inspect the AX tree, use browser MCP, or consume/invalidate
snapshot state first prefer the current CLI build's deterministic daemon-<build>.sock and may auto-start it before
considering the GUI host. Explicit Bridge paths, custom daemon paths, application inventory or launch, and local-only
execution bypass that preference.
Automatic migration defers while operational requests are active and keeps using the legacy daemon for that invocation.
Older daemons without conditional stop remain on bridge.sock until they exit or are explicitly stopped. Explicit
daemon start asks the user to stop those older daemons first, and asks for a retry when supported daemons are busy.
If an incompatible daemon already owns daemon.sock, automation uses a build-scoped fallback. Default status reports
the compatible fallback and warns about the additional daemon; start promotes an idle, safely stoppable fallback from
auto to persistent manual mode on the same socket.
Concrete ps1_ snapshot references are not routed by these daemon preferences. Peekaboo selects the one authenticated
local, daemon, or GUI Bridge producer that claims the reference and refuses before dispatch if ownership is missing or
ambiguous. Explicit socket and local-only options remain strict; see
Bridge snapshot authority.
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.
- 2d ago First seen · 80 lines · 0 tokens per session scan A 4136ec594dc6
daemon is a command published in the GitHub repository openclaw/Peekaboo (5,098 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 921 tokens. 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 commands, from other repositories
upload
Archive, upload, and submit to external TestFlight (full loop with monitor).
release
Create a new Remarc release using the automated GitHub Actions workflow.
imark-review
Open a markdown document in Imark for review and wait for the reviewer's notes.
imark-notes
Read the Imark comments out of a markdown file.
archive
Create xcarchive for TestFlight.
build
Build debug and launch HomeClaw.