verify

A browser-based check for verifying changes to the ClawStash app, including how its interface behaves during real user actions. It uses a separate temporary database for testing.

In plain words
What is it for?
Use it after substantial frontend changes to launch the app, create and edit stashes, open overlays, test shortcuts, and verify key browser flows.
Why use it?
It catches timing and interaction problems that type checks and automated tests may miss.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/fo0/clawstash/verify
Any agent
npx skills add fo0/clawstash --skill verify
Clone the repo
git clone --depth 1 https://github.com/fo0/clawstash

Made for: Claude Code, Codex.

Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 557 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00054 $0.00557
Opus 5 $0.00027 $0.00279
Sonnet 5 $0.00011 $0.00111
Haiku 4.5 $0.00005 $0.00056

Measured 2d ago against content hash 2345abd83085, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

verify scanned grade A with 1 finding 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 2d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

# server is up when: curl -s -o /dev/null -w "%{http_code}" http://localhost:3100/ -> 200 (~1-5 s)
.claude/skills/verify/SKILL.md · 47 lines

What it actually says

Verify ClawStash in a real browser

Launch

npm install                # fresh containers start without node_modules
DATABASE_PATH=/tmp/verify.db PORT=3100 npm run dev   # isolated scratch DB, non-default port
# server is up when: curl -s -o /dev/null -w "%{http_code}" http://localhost:3100/ -> 200 (~1-5 s)

Use a scratch DATABASE_PATH outside the repo — never let a verification run create or touch ./data/.

Drive

Chromium is pre-installed for Playwright in remote sessions (/opt/pw-browsers/chromium-*/chrome-linux/chrome; ls /opt/pw-browsers/). The repo does not depend on Playwright — install playwright-core into a scratch dir (NOT the repo) and point chromium.launch({ executablePath }) at the pre-installed binary. Do not run playwright install.

Useful selectors/flows that exist today:

  • Create stash: .btn-new-stash#stash-name, .file-name-input, .code-editor-wrapper textarea, button:has-text("Save Stash").
  • Viewer URL shape: /stash/<uuid>; editor: /stash/<uuid>/edit.
  • Overlays: ?.shortcuts-help-dialog, Alt+K.search-overlay.
  • Global hotkeys (n, e, a, Escape) are inert while typing in inputs — to exercise them, focus a button/heading first.
  • Dirty-editor guards use window.confirm — handle Playwright dialog events.
  • Graph: /graph, canvas .graph-canvas; hit-test nodes by probing a small click grid around the canvas center.

Gotchas

  • Run npm run format (pinned Prettier from node_modules) before judging git status — hooks/other Prettier versions can reformat files you never touched; the pinned run restores them.
  • npm install with a different npm major may churn package-lock.json (e.g. libc fields). If you added no dependency, git checkout -- package-lock.json.
  • Kill the dev server before committing (pkill -f "next dev").
Changes

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.

  1. 2d ago First seen · 47 lines · 54 tokens per session scan A 2345abd83085

Subscribe to this mod's changes

verify is a skill published in the GitHub repository fo0/clawstash (1 stars, last pushed yesterday), licensed MIT. It adds 54 tokens to every session and 557 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

blazemeter-recorders

Comprehensive guide for BlazeMeter Recorders, including Chrome Extension and Proxy Recorder. Use when working with recorders for (1) Recording tests with Chrome Extension, (2) Creating and using Proxy Recorder, (3) Configuring browsers and devices for proxy recording, (4) Setting port ranges for proxy recorder, or any…

Blazemeter/bzm-mcp · 76 tokens

@elad12390/web-research-assistant

Comprehensive MCP server for web research with 14 tools: SearXNG + Exa AI search, URL crawling, stealth scraping (Cloudflare bypass), package registry lookup (npm/PyPI/crates), GitHub stats, changelog fetching, tech comparison, error translation, API docs discovery, stock image search, and service health. Trigger…

elad12390/web-research-assistant · 144 tokens

qa-runner

Use when asked to "run QA", "qa check", "test checklist", or execute QA checklists against a running app via browser automation. Requires the browser-bridge MCP server and Chrome extension.

adbarc92/mcp-browser-bridge · 44 tokens

lastest

Lastest is a visual regression testing platform. It records browser tests, runs them via Playwright, diffs screenshots, and uses AI to classify changes. Available as an MCP server for AI agent integration.

las-team/lastest · 0 tokens

qa

QA test a live website with Axon discovery/content evidence plus browser automation when interaction is required. Use when the user wants exploratory QA, form testing, navigation/link checks, responsive checks, performance observations, bug reports, or a pre-launch quality review.

dinglebear-ai/axon · 52 tokens

field-test

Exercise tools, resources, and prompts against a live HTTP server via MCP JSON-RPC over curl. Starts the server, surfaces the catalog, runs real and adversarial inputs, and produces a tight report with concrete findings and numbered follow-up options. Use after adding or modifying definitions, or when the user asks to…

cyanheads/pubmed-mcp-server · 76 tokens