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/visualizergit 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.00335 |
| Opus 5 | $0.00000 | $0.00168 |
| Sonnet 5 | $0.00000 | $0.00067 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
visualizer 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.
What it actually says
peekaboo visualizer
Runs a lightweight smoke sequence for the three v4 visualizer surfaces: the agent cursor, app-anchored input HUD, and capture indicators.
These are three feedback categories, not the complete settings surface: Peekaboo.app also has a visualizer master switch, a menu-bar app-icons switch, and playback controls.
What it does
- Connects to the visualizer host (typically
Peekaboo.app) - Emits representative cursor, input HUD, and capture-indicator events
Usage
peekaboo visualizer
peekaboo visualizer --json > .artifacts/playground-tools/visualizer.json
Notes
- This is primarily a manual visual check: success means the command exits 0, dispatches all visualizer events, and you can see the overlay sequence render.
- The smoke command deliberately previews overlays. Production targeted background input never emits cursor or input-HUD overlays, even when the target window is visible or frontmost; only untargeted or explicitly foreground input may show them.
- If the visualizer host is not available, the command fails fast instead of pacing through the full animation sequence.
- If nothing appears, verify:
Peekaboo.appis running and reachable- permissions are granted (
peekaboo permissions status) - your screen isn’t being captured by another app that blocks overlays
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 · 32 lines · 0 tokens per session scan A 7b0570fddae6
visualizer 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 335 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.
generate-story
Generate an agentic, fact-grounded relationship story visualization for "$ARGUMENTS".
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.