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/github/awesome-copilot/devtools-regression-investigatorgit clone --depth 1 https://github.com/github/awesome-copilotWrote 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/github/awesome-copilot/devtools-regression-investigator)<a href="https://agentmods.dev/agents/github/awesome-copilot/devtools-regression-investigator"><img src="https://agentmods.dev/badge/agents/github/awesome-copilot/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 | $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 today.
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 — 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.
- today First seen · 126 lines · 32 tokens per session scan A 3abbdc407b6a
DevTools Regression Investigator is an agent published in the GitHub repository github/awesome-copilot (38,623 stars, last pushed today), licensed MIT. 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other agents, from other repositories
python-architect
Expert on Python design patterns, modularization, and scalable architecture for the APM CLI codebase. Activate when creating new modules, refactoring class hierarchies, or making cross-cutting architectural decisions.
cdo
APM Chief Documentation Officer. Use this agent as the synthesizer and final arbiter for any multi-persona docs panel -- holds the 3-promise narrative (consume / produce / govern), the chapter-start and chapter-end bridges, the TOC integrity, and the persona ramps (consumer / producer / enterprise). Activate to…
apm-expert
Expert on APM (Agent Package Manager). Helps users install, configure, author, and troubleshoot APM packages, dependencies, compilation, MCP servers, and governance policies.
test-coverage-expert
Test-coverage expert paired with the DevX UX lens. Activate when reviewing PRs that change CLI surface (commands, flags, help text), error wording, exit codes, install/init/run flows, lockfile behavior, auth resolution, hooks, marketplace, or any contract a user can observe -- even when the user does not say "tests"…
devx-ux-expert
Developer Tooling UX expert specialized in package manager mental models (npm, pip, cargo, brew). Activate when designing CLI command surfaces, install/init/run flows, error ergonomics, or first-run experience for the APM CLI.
editorial-owner
APM documentation editorial owner. Use this agent for tone, voice, pragmatism, and readability checks across documentation drafts. Activate whenever doc-writer output needs a final tone-and-clarity pass before publishing -- catches bloat, abstract jargon, marketing voice, redundant explanations, and any prose that…