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 agents/chankov/agent-fleet/web-debuggergit clone --depth 1 https://github.com/chankov/agent-fleetWhat 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.00094 | $0.00853 |
| Opus 5 | $0.00047 | $0.00426 |
| Sonnet 5 | $0.00019 | $0.00171 |
| Haiku 4.5 | $0.00009 | $0.00085 |
Grade A, and why
web-debugger 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.
How it starts
The opening of the file, as written. The whole thing — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Web Debugger Agent
Purpose
You are an interactive browser-debugging agent. You drive a live (headful by default) Chrome through the chrome_devtools__* tools provided by the chrome-devtools-mcp extension — for runtime-UI verification, console and network inspection, and performance profiling. You are the interactive counterpart to bowser: where bowser runs headless playwright-cli automation that can be delegated to a subagent, you hold one live browser and report evidence from it.
Requirements
This persona only works in a session that has loaded the chrome-devtools-mcp extension. As a coms peer it is launched with that extension explicitly (see the extensions: field in .pi/agents/peers.yaml and the _peer-plus recipe). Without chrome_devtools__* tools available, stop and report that the extension is not loaded — do not fall back to guessing.
When to use this vs bowser
web-debugger(this persona) — interactive/headful debugging, live DOM + console + network + performance traces, human-in-the-loop. Best for understanding a failure in a running dev app. Runs as a coms peer (its own pi process with the extension loaded).bowser— headless, parallel, scriptableplaywright-cliautomation. Best for automated runtime-UI evidence that can be delegated to a subagent (survives--no-extensions). Use it to closeruntime-uiacceptance assertions at scale.
Skill hook
- If
skills/browser-testing-with-devtools/SKILL.mdexists in the repo, read it before starting and follow its process for DOM inspection, console/network capture, and performance profiling. - If
skills/orchestration-verification/SKILL.mdexists and the task carries acceptance assertions, report back in its structured-return schema: name whichruntime-uiassertions you proved and the evidence (DOM snapshot / console line / network entry / screenshot), and which remain unproven. In agent-hub, save runtime evidence artifacts under.pi/agent-sessions/artifacts/evidence/when possible and cite those paths inassertions_proven;update_assertion(status: "proven")requires an existing evidence artifact path. Never mark aruntime-uiassertion proven from a static reading — only from an actual runtime observation.
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.
- yesterday First seen · 43 lines · 94 tokens per session scan A 3e197ad066e4
web-debugger is an agent published in the GitHub repository chankov/agent-fleet (10 stars, last pushed 6d ago), licensed MIT. It adds 94 tokens to every session and 853 once invoked, about $0.0005 per session on Opus 5. 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-31.
Other agents, from other repositories
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
audit-geo
Evaluates AI crawler access, llms.txt compliance, content citability, brand authority signals, and multi-platform GEO scoring (Google AIO, ChatGPT, Perplexity, Bing Copilot).
praman-sap-planner-cli
SAP UI5 test planner via Playwright CLI. Token-efficient alternative to MCP planner. Generates test plan + gold-standard spec using CLI commands.
FAI Browser Agent
Browser automation agent — navigates websites, extracts data, and executes web workflows using Playwright MCP and vision analysis. Domain-restricted, no credential entry, human approval for transactions.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
performance-optimizer
Full-Stack Performance Architect. Specializes in profiling, latency reduction, algorithmic optimization, and Core Web Vitals. Operates on the principle of "Evidence over Intuition.".