clawstash: Skill for Claude Code

.claude/skills/verify/SKILL.md

verify is a skill for Claude Code from fo0/clawstash. It costs 54 tokens per session (557 once invoked), scanned A, original, MIT.

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 Code

Written for Claude Code: installed under .claude/.

This is fo0/clawstash's own configuration. It tells Claude Code how to work on clawstash itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything clawstash configures →

Reuse

Borrowing it

Nothing to install: this file belongs to fo0/clawstash. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/fo0/clawstash/main/.claude/skills/verify/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/fo0/clawstash

Made for: Claude Code.

Wrote 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.

agentmods badge for verify

README.md
[![agentmods](https://agentmods.dev/badge/skills/fo0/clawstash/verify/github.svg)](https://agentmods.dev/skills/fo0/clawstash/verify)
Your own site
<a href="https://agentmods.dev/skills/fo0/clawstash/verify"><img src="https://agentmods.dev/badge/skills/fo0/clawstash/verify/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.

agentmods 80×15 button for verify

Your own site · 80×15
<a href="https://agentmods.dev/skills/fo0/clawstash/verify"><img src="https://agentmods.dev/badge/skills/fo0/clawstash/verify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
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. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00054 $0.00557
Opus 5.5 $0.00022 $0.00223
Sonnet 5.5 $0.00011 $0.00111
Haiku 4.5 $0.00005 $0.00056

Measured 2mo ago against content hash 2345abd83085, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2mo 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. 2mo 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 today), licensed MIT. It adds 54 tokens to every session and 557 once invoked, about $0.0002 per session on Opus 5.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

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

playwright

Playwright end-to-end testing expertise for modern web applications. Covers browser automation, cross-browser testing, API testing, visual regression, and CI integration. Use for E2E testing of web apps across Chromium, Firefox, and WebKit.

Plazmodium/odin-workflow · 51 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, measures every call (bytes, token estimate, wall-clock) and weighs the catalog, renders app tools' views in a headless MCP Apps host, and produces a…

cyanheads/pubmed-mcp-server · 106 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, measures every call (bytes, token estimate, wall-clock) and weighs the catalog, renders app tools' views in a headless MCP Apps host, and produces a…

cyanheads/pokeapi-mcp-server · 106 tokens

smoke-test

Run smoke tests against a deployed or local app based on your git diff. Each test uses Skyvern browser tools (navigate, act, validate, screenshot) with Chrome DevTools MCP as fallback. Posts screenshot evidence as PR comments.

Skyvern-AI/skyvern · 50 tokens