peek

Install

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.

Security

Grade A, and why

peek 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 yesterday.

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.

.claude-plugin/marketplace.json · 16 lines

What it actually says

{
  "name": "peek",
  "owner": { "name": "Cubenest" },
  "description": "peek — local-first browser-session forensics + repro for AI coding agents.",
  "renames": { "peek": "peekdev" },
  "plugins": [
    {
      "name": "peekdev",
      "source": "./plugins/peek",
      "description": "Let your AI coding agent debug what already happened in your real browser — and, with per-origin consent, act in the live page. Local-first rrweb session forensics over MCP.",
      "homepage": "https://peek.cubenest.in",
      "license": "Apache-2.0"
    }
  ]
}

Changes

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.

Related

Other plugins, from other repositories