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.
git clone --depth 1 https://github.com/roy2392/vibe-agents-rulesWrote 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/rules/roy2392/vibe-agents-rules/mcp-peekaboo-setup)<a href="https://agentmods.dev/rules/roy2392/vibe-agents-rules/mcp-peekaboo-setup"><img src="https://agentmods.dev/badge/rules/roy2392/vibe-agents-rules/mcp-peekaboo-setup.svg" alt="Measured on agentmods" 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.00011 | $0.00868 |
| Opus 5 | $0.00005 | $0.00434 |
| Sonnet 5 | $0.00002 | $0.00174 |
| Haiku 4.5 | $0.00001 | $0.00087 |
Grade C, and why
mcp-peekaboo-setup scanned grade C with 1 finding 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.
Harvests environment variableshighData exfiltration
Enumerating or grepping the environment for keys collects credentials unrelated to what the mod says it does.
# Extract API key from .zshrc This is a copy
100% identical to mcp-peekaboo-setup — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Peekaboo Setup
This rule sets up the Peekaboo MCP server, which provides screenshot capture and AI-powered vision analysis capabilities.
Overview
Peekaboo is a Model Context Protocol server that enables Claude to:
- Take screenshots of your screen
- Analyze images using AI vision models
- Support both OpenAI and Ollama providers
Prerequisites
- macOS 14.0+ (Sonoma or later)
- Node.js 20.0+
- OpenAI API key (stored in
~/.zshrc) - Optional: Ollama with vision models installed
Configuration
Add this to your Claude Desktop configuration (~/Library/Application Support/Claude/claude_desktop_config.json):
{
"mcpServers": {
"peekaboo": {
"command": "npx",
"args": [
"-y",
"@steipete/peekaboo-mcp"
],
"env": {
"PEEKABOO_AI_PROVIDERS": "openai/gpt-4o,ollama/llava:latest",
"OPENAI_API_KEY": "<READ_FROM_ZSHRC>",
"PEEKABOO_LOG_LEVEL": "info",
"PEEKABOO_DEFAULT_SAVE_PATH": "~/Desktop"
}
}
}
}
Security Setup
To securely extract the OpenAI API key from ~/.zshrc:
# Extract API key from .zshrc
export OPENAI_API_KEY=$(grep "export OPENAI_API_KEY=" ~/.zshrc | cut -d'"' -f2)
# Update Claude config with the actual key
jq --arg key "$OPENAI_API_KEY" \
'.mcpServers.peekaboo.env.OPENAI_API_KEY = $key' \
~/Library/Application\ Support/Claude/claude_desktop_config.json > tmp.json && \
mv tmp.json ~/Library/Application\ Support/Claude/claude_desktop_config.json
Available Tools
Once configured, you'll have access to:
-
peekaboo_capture_screenshot
- Takes a screenshot of the entire screen or a specific display
- Saves to the default path or specified location
-
peekaboo_analyze_screenshot
- Captures and analyzes a screenshot with AI
- Uses the configured AI providers for vision analysis
Usage Examples
Basic Screenshot
Take a screenshot of my screen
Screenshot with Analysis
Take a screenshot and tell me what application is currently in focus
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 · 134 lines · 11 tokens per session scan C 076a2b7243e7
mcp-peekaboo-setup is a cursor rule published in the GitHub repository roy2392/vibe-agents-rules (11 stars, last pushed 1y ago), licensed MIT. It adds 11 tokens to every session and 868 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (harvests environment variables). It is 100% identical to mcp-peekaboo-setup, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
webkit-browser
Cursor rule "webkit-browser" from duckduckgo/apple-browsers, covering webkit & browser development guidelines, webview configuration, basic webview setup, user scripts management and tab management.
vasu-playwright-utils
../../templates/cursor-rules/vasu-playwright-utils.mdc.
chrome-extension-manifest-rules
Specific rules related to the Chrome extension manifest file, ensuring proper structure and content.
vla-registry
Multi-model GUI/VL registry — browser wllama grounding (ShowUI-2B is default + E2E gate).
dev-browser
Fallback browser automation with persistent Chrome state. Use only when Browser Use is unavailable or blocked.
safari
This file, safari.mdc, serves as a repository for detailed working notes, observations, and learnings acquired during the process of automating Safari interactions, particularly for the MCP Inspector UI. It's intended to capture the nuances of trial-and-error, debugging steps, and insights into what worked, what…