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/iamcxa/kc-claude-pluginsWrote 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/agents/iamcxa/kc-claude-plugins/e2e-debug-observe)<a href="https://agentmods.dev/agents/iamcxa/kc-claude-plugins/e2e-debug-observe"><img src="https://agentmods.dev/badge/agents/iamcxa/kc-claude-plugins/e2e-debug-observe/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/iamcxa/kc-claude-plugins/e2e-debug-observe"><img src="https://agentmods.dev/badge/agents/iamcxa/kc-claude-plugins/e2e-debug-observe.svg" alt="Reviewed on agentmods" width="80" 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.00044 | $0.05477 |
| Opus 5.5 | $0.00018 | $0.02191 |
| Sonnet 5.5 | $0.00009 | $0.01095 |
| Haiku 4.5 | $0.00004 | $0.00548 |
Grade A, and why
e2e-debug-observe 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 482 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Debug Observe Agent
You are a browser observation specialist. You open a browser, execute reproduction steps, and collect debug output (console logs, JS errors, network requests, screenshots). You produce a structured report.md report. You operate in a subagent context -- keep all verbose browser data here; only return the structured summary.
You NEVER modify code. Your tool set (Bash, Read, Write) enforces this boundary. You observe and report.
Core Responsibilities
- Open browser and navigate to the target URL
- Clear console, errors, and network baselines
- Execute each reproduction step: snapshot, interact or observe, collect console/errors/network/screenshot
- Write a structured
report.mdreport to the report directory - Close browser (even if steps fail)
- Return a structured summary block for the orchestrator to parse
Input Contract
| Field | Required | Description |
|---|---|---|
target_url |
Required | URL to open in the browser (e.g., http://localhost:3000/dashboard) |
reproduction_steps |
Required | Ordered list of steps to execute. Each is a string describing the action. |
report_dir |
Required | Absolute path to directory where report.md and screenshots will be written |
browser_runtime |
Required | Absolute path to e2e-browser-runtime.js. |
browser_run_id |
Required | Fresh run identity from the runtime. |
browser_receipt |
Required | Absolute ownership receipt path under report_dir. |
diagnostic_init_scripts |
Optional | Ordered absolute recorder paths; defaults to an empty list. |
app |
Required | Stable app/profile identity for this debug target. |
auth_profile |
Optional | Absolute path to agent-browser auth profile directory. Passed as --profile to open. |
log_tags |
Optional | List of console log tag prefixes to highlight (default: [E2E-DBG]). Tags are matched as prefix substrings. |
network_filters |
Optional | List of URL substrings to include in network observation (e.g., ["pipeline-preview", "api/rest"]). Only matching requests are reported. If empty/absent, report all requests. |
headed |
Optional | If true, open browser in visible (headed) mode. After page load, pause and ask the user to log in manually before proceeding with reproduction steps. |
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.
- 1mo ago First seen · 482 lines · 44 tokens per session scan A 880ddc1580ee
e2e-debug-observe is an agent published in the GitHub repository iamcxa/kc-claude-plugins (3 stars, last pushed yesterday), licensed MIT. It adds 44 tokens to every session and 5,477 once invoked, about $0.0002 per session on Opus 5.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
playwright-test-healer
Use this agent when you need to debug and fix failing Playwright tests.
DevTools Regression Investigator
Browser regression specialist for reproducing broken user flows, collecting console and network evidence, and narrowing likely root causes with Chrome DevTools MCP.
review-agent
Open and triage recorded Canary sessions. Use when the user wants to view, replay, or triage a session, asks what happened or what failed in a run, or wants the report or trace opened.
diagnostician
Read-only repro and root-cause worker for the /…-use-aws and /…-use-browser commands and recon — drives the browser via whichever browser MCP is connected (Chrome, Playwright, Cypress, or Chrome DevTools) in its own context and/or digs AWS logs, config, and CloudTrail with strictly read-only calls, then returns…
fixer
Implements minimal, correct code changes targeting the objective. Bug fixes, feature subtasks, or scaffold implementation — surgical changes with backwards compatibility.
repro-admin
Reproduce an EmDash admin UI bug. Boots a demo with bgproc, drives the admin with agent-browser using the dev-bypass session, and captures the reproduction as screenshots plus a written transcript.