Borrowing it
Nothing to install: this file belongs to mxrsv/spacevibe-deck. 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/mxrsv/spacevibe-deck/main/.claude/skills/test-deck-app/SKILL.mdgit clone --depth 1 https://github.com/mxrsv/spacevibe-deckWrote 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/mxrsv/spacevibe-deck/test-deck-app)<a href="https://agentmods.dev/skills/mxrsv/spacevibe-deck/test-deck-app"><img src="https://agentmods.dev/badge/skills/mxrsv/spacevibe-deck/test-deck-app/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/mxrsv/spacevibe-deck/test-deck-app"><img src="https://agentmods.dev/badge/skills/mxrsv/spacevibe-deck/test-deck-app.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.00074 | $0.01254 |
| Opus 5.5 | $0.00030 | $0.00502 |
| Sonnet 5.5 | $0.00015 | $0.00251 |
| Haiku 4.5 | $0.00007 | $0.00125 |
Grade A, and why
test-deck-app 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 10d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Deck in Electron
The gate in AGENTS.md applies to a new
user-facing feature or a changed UI flow. It does not apply to bug fixes, styling, copy,
refactors, tests or docs. The browser preview (npm run dev) paints the shell but reaches no
IPC, PTY, persistence or updater, so a pass there proves nothing.
If the app cannot be launched (no display, build fails, Electron missing), report the blocker and stop. Do not substitute the browser preview or another automation tool.
Launch an isolated instance
-
In the checkout under test:
npm run build && npm run electron:build. In a fresh worktreenode_modules/electron/distmay be missing afternpm install; runnode node_modules/electron/install.jsonce. -
Make a scratch directory outside the repo for
userData, aCLAUDE_CONFIG_DIR, and stub agents. A plainelectron:devrun shares the owner's realworkspaces.jsonandsession.json. -
Launch from a scratch driver with
playwright-core:const { _electron } = require("playwright-core"); const app = await _electron.launch({ executablePath: "<checkout>/node_modules/electron/dist/Electron.app/Contents/MacOS/Electron", args: ["<checkout>/.claude/skills/test-deck-app/scripts/isolated-main.cjs"], env: { ...cleanEnv, // process.env without CLAUDECODE, DECK_AGENT_ID, DECK_AGENT_PID, DECK_AGENT_NESTED DECK_TEST_USERDATA: "<scratch>/userdata", DECK_TEST_MAIN: "<checkout>/dist-electron/electron/main.cjs", CLAUDE_CONFIG_DIR: "<scratch>/claude", }, }); const page = await app.firstWindow();isolated-main.cjssetsuserDatabefore main loads and refuses to start without both variables.
Traps that cost a run
- A stub, never a real agent. Put stubs on a scratch
PATHset in a scratchZDOTDIR/.zshrc(overridepath_helper), and never seedlastAgent: "claude": it starts a real, unattended session. Unset theCLAUDECODEvariables above, or Deck's wrappers treat the pane as nested and a probe reads like plain agent behaviour. - One instance per userData. The single-instance lock is per directory: a second launch on the same one exits 0 with no window and Playwright reports a closed target.
setViewportSizepinsinnerWidth. After any window resize, call it again withBrowserWindow.getAllWindows()[0].getContentSize()and readinnerWidthbefore measuring.app.close()hangs. End withapp.evaluate(({ app }) => app.exit(0)).app.getVersion()reports Electron's version from a wrapper outside the packaged app. Expected, not a bug.- To record links Deck would open, reassign
shell.openExternalinapp.evaluatebefore the flow starts.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago Changed · +28 lines 16b6e37cb32c
- 13d ago First seen · 67 lines · 74 tokens per session scan A 8a248826ee11
test-deck-app is a skill published in the GitHub repository mxrsv/spacevibe-deck (41 stars, last pushed 3d ago), licensed MIT. It adds 74 tokens to every session and 1,254 once invoked, about $0.0003 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-15.
Other skills, from other repositories
verify-ui-change-in-cloud
Verifies user-facing Warp client changes by spawning a cloud agent with computer use to test Warp. Use only when the user explicitly requested computer-use verification or accepted an offer to run it, and ONLY in non-sandboxed environments and local environments. Triggers a cloud agent that runs the test-warp-ui skill.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.
tui-explorer
Discover and replay terminal UI paths using agent-tui. Use when you need to launch a TUI app, explore navigation with bounded BFS, generate markdown acceptance tests, and verify those tests repeatedly. Do not use for web or desktop GUI automation.
agent-tui
Automate terminal UI (TUI) apps with agent-tui for testing, inspection, demos, and scripted interactions. Use when automating CLI/TUI flows, regression testing terminal apps, verifying interactive behavior, or extracting structured text from terminal UIs. Also use when asked what agent-tui is, how it works, or to demo…
qa-testing
Verify your work by actually operating the app or website you changed, instead of assuming it works. Strongly recommended whenever you build, modify, or debug a web app, website, or desktop GUI app. Drive real browsers with the agent-browser CLI and native desktop apps with the cua-driver CLI. These are installed on…
verify
Exercise the real app/API/CLI and collect observable evidence; tests alone do not count as end-to-end verification.