DevSpace is a self-hosted Model Context Protocol server that lets ChatGPT work with approved projects on a user’s own computer. It enables ChatGPT to inspect and edit files, search code, run terminal commands, and use isolated Git worktrees. The catalogue entries provide agents, a skill, and an instruction for using this local coding workflow.
Borrowing it
Nothing to install: this file belongs to Waishnav/devspace. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Waishnav/devspace/main/.agents/skills/replay-qa/SKILL.mdgit clone --depth 1 https://github.com/Waishnav/devspaceWrote 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/skills/waishnav/devspace/replay-qa)<a href="https://agentmods.dev/skills/waishnav/devspace/replay-qa"><img src="https://agentmods.dev/badge/skills/waishnav/devspace/replay-qa/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/skills/waishnav/devspace/replay-qa"><img src="https://agentmods.dev/badge/skills/waishnav/devspace/replay-qa.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.00058 | $0.01086 |
| Opus 5.5 | $0.00023 | $0.00434 |
| Sonnet 5.5 | $0.00012 | $0.00217 |
| Haiku 4.5 | $0.00006 | $0.00109 |
Grade A, and why
replay-qa 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Replay QA
pnpm qa replays scenario tool calls against a fresh DevSpace server, renders every card in a local MCP Apps host, and captures evidence with agent-browser.
Each run is isolated: its own HOME, config, SQLite state, worktree root, allowed root, and Git fixture under .devspace-dev/qa/runs/<timestamp>/<scenario>/. Ports are allocated dynamically, so runs never replace an existing process.
Run
pnpm qa --list # scenarios and descriptions
pnpm qa # every scenario
pnpm qa codex-edit-review # one scenario
pnpm qa --theme dark codex-edit-review
pnpm qa --bare-host codex-edit-review # host sends a theme but no style variables
pnpm qa --checkout ../other-worktree # QA another checkout with this harness
pnpm qa --no-build ... # skip `pnpm build:app` in the target checkout
The exit code is non-zero when a step fails its expectations, a card does not initialize or render, or the page reports errors.
Each run directory contains:
report.md: pass/fail per step, card state and height, failures, and screenshot paths. Read this first.transcript.json: the tool list, every request and response, UI resources, and calls the cards made back to the server.server.log: the DevSpace server's JSON log.artifacts/: a full-page screenshot, one screenshot per card, an accessibility snapshot, the browser console, anderrors.json.
Look at the screenshots before reporting UI behavior. A passing report means that cards rendered, not that they look right.
Interact with cards
pnpm qa --serve --no-browser codex-edit-review # prints the host URL and keeps running
export AGENT_BROWSER_SESSION=devspace-qa
agent-browser open "<host url>"
agent-browser wait --fn "window.__devspaceQa?.settled === true"
agent-browser snapshot -i # card iframes appear inline with their buttons
agent-browser click @e12 # e.g. expand a file in the show_changes card
agent-browser screenshot "#step-3" /tmp/after.png
agent-browser close
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 · 94 lines · 58 tokens per session scan A 5a33b4a99ba0
replay-qa is a skill published in the GitHub repository Waishnav/devspace (5,296 stars, last pushed yesterday), licensed MIT. It adds 58 tokens to every session and 1,086 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-10-27.
Other skills, from other repositories
dogfood
Exploratory QA of web apps: find bugs, evidence, reports.
verify
Verify that a code change actually does what it's supposed to by exercising it end-to-end and observing behavior — drive the affected flow, not just tests or typecheck. Run before committing nontrivial changes; bootstraps this repo's project verify skill if none exists yet. Don't invoke it on a diff that only touches…
vscode-visual-regression
Write Storybook stories and visual regression tests for the Kilo VS Code extension webview UI.
web-gui-tester
Use the browser automation tooling available in the session to test web frontends interactively in a purely GUI-based, black-box manner: simulate real user clicks, text input, scrolling, and other actions; use screenshots for visual verification and read-only DOM inspection for cross-validation; and produce a final…
verify
Exercise the real app/API/CLI and collect observable evidence; tests alone do not count as end-to-end verification.
webapp-testing
Start/reuse a local app, wait for readiness, inspect rendered state/console/network, act from observed selectors, and verify with evidence.