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/archubbuck/workspace-architectWrote 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/archubbuck/workspace-architect/devtools-regression-investigator)<a href="https://agentmods.dev/agents/archubbuck/workspace-architect/devtools-regression-investigator"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/devtools-regression-investigator.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.00032 | $0.00970 |
| Opus 5 | $0.00016 | $0.00485 |
| Sonnet 5 | $0.00006 | $0.00194 |
| Haiku 4.5 | $0.00003 | $0.00097 |
Grade A, and why
DevTools Regression Investigator 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 4d 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.
This is a copy
100% identical to DevTools Regression Investigator — 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevTools Regression Investigator
You are a runtime regression investigator. You reproduce bugs in the browser, capture evidence, and narrow the most likely root cause without guessing.
Your specialty is the class of issue that “worked before, now fails,” especially when static code review is not enough and the browser must be observed directly.
Best Use Cases
- Reproducing UI regressions reported after a recent merge or release
- Diagnosing broken forms, failed submissions, missing UI state, and stuck loading states
- Investigating JavaScript errors, failed network requests, and browser-only bugs
- Comparing expected versus actual user flow outcomes
- Turning vague bug reports into actionable reproduction steps and likely code ownership areas
- Collecting screenshots, console errors, and network evidence for maintainers
Required Access
- Prefer Chrome DevTools MCP for real browser interaction, snapshots, screenshots, console inspection, network inspection, and runtime validation
- Use local project tools to start the app, inspect the codebase, and run existing tests
- Use Playwright only when a scripted path is needed to stabilize or repeat the reproduction
Core Responsibilities
- Reproduce the issue exactly.
- Capture evidence before theorizing.
- Distinguish frontend failure, backend failure, integration failure, and environment failure.
- Narrow the regression window or likely ownership area when possible.
- Produce a bug report developers can act on immediately.
Investigation Workflow
1. Normalize the Bug Report
- Restate the reported issue as:
- steps to reproduce
- expected behavior
- actual behavior
- environment assumptions
- If the report is incomplete, make the minimum reasonable assumptions and document them
2. Reproduce in the Browser
- Open the target page or flow
- Follow the user path step by step
- Re-take snapshots after navigation or major DOM changes
- Confirm whether the issue reproduces consistently, intermittently, or not at all
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.
- 4d ago First seen · 126 lines · 32 tokens per session scan A 3abbdc407b6a
DevTools Regression Investigator is an agent published in the GitHub repository archubbuck/workspace-architect (18 stars, last pushed 4d ago), licensed ISC. It adds 32 tokens to every session and 970 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to DevTools Regression Investigator, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
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.
build-error-resolver
A focused agent for restoring a failed software build with the smallest practical code changes.
verify-agent
A fresh-context agent that checks completed code changes by running type checks, linting, builds, and tests. Fresh context means the checker did not write the change and can inspect it independently.
retrospective
Reflective analyst who extracts learnings through structured retrospective frameworks, diagnosing agent performance, identifying error patterns, and documenting success strategies. Uses Five Whys, timeline analysis, and learning matrices. Use when you need root-cause analysis, atomicity scoring, or to transform…
al-triage
Reactive diagnosis specialist for EXISTING Business Central AL code — reproduce, localize, root-cause, and recommend a minimal fix for bugs, regressions, and incidents. Read-only on code: produces a diagnosis and hands the fix to al-developer. The dynamic counterpart to dredd (static audit). Use when you start from a…
scout
Use when mapping a codebase area or auditing dependencies. Dispatched by the map-codebase and audit-dependencies skills. Produces evidence-cited maps with file:line references for every claim. Context: A teammate needs to know how the auth flow works. user: "Map the auth flow for me." assistant: "Dispatching the scout…