dev3000

A web debugging assistant that collects server logs, browser activity, console messages, network requests, and screenshots in one timeline. It also starts the development runtime and uses a monitored browser.

In plain words
What is it for?
Use it to investigate web-app problems by comparing server output, browser events, network traffic, console errors, and screenshots.
Why use it?
It puts information from different parts of a web app in time order, making it easier to see what happened around a bug.

Plugin for Claude Code

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.

Claude Code
/plugin marketplace add pleaseai/claude-code-plugins
agentmods
npx agentmods add plugins/pleaseai/claude-code-plugins/dev3000
Clone the repo
git clone --depth 1 https://github.com/pleaseai/claude-code-plugins

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

dev3000 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.

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.

plugins/dev3000/.claude-plugin/plugin.json · 22 lines

What it actually says

{
  "name": "dev3000",
  "version": "1.2.0",
  "description": "dev3000 (d3k) debugging assistant — captures server logs, browser events, console messages, network requests, and screenshots into a unified, timestamped timeline for AI debugging. Bootstraps d3k as the dev runtime and drives its monitored browser instead of running npm/bun dev directly.",
  "author": {
    "name": "Vercel Labs",
    "url": "https://github.com/vercel-labs"
  },
  "homepage": "https://github.com/vercel-labs/dev3000",
  "repository": "https://github.com/vercel-labs/dev3000",
  "license": "MIT",
  "keywords": [
    "dev3000",
    "d3k",
    "debugging",
    "web",
    "logs",
    "screenshots"
  ],
  "skills": "./.agents/skills/"
}
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.

  1. yesterday First seen · 22 lines scan A 0eeab449ff0c

Subscribe to this mod's changes

dev3000 is a plugin published in the GitHub repository pleaseai/claude-code-plugins (13 stars, last pushed 7d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.