Borrowing it
Nothing to install: this file belongs to ktnyt/cclsp. 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/ktnyt/cclsp/main/.claude/skills/hands-on-test/SKILL.mdgit clone --depth 1 https://github.com/ktnyt/cclspWrote 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/ktnyt/cclsp/hands-on-test)<a href="https://agentmods.dev/skills/ktnyt/cclsp/hands-on-test"><img src="https://agentmods.dev/badge/skills/ktnyt/cclsp/hands-on-test.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.1 | $0.00069 | $0.01713 |
| Opus 5 | $0.00034 | $0.00856 |
| Sonnet 5 | $0.00014 | $0.00343 |
| Haiku 4.5 | $0.00007 | $0.00171 |
Grade A, and why
hands-on-test 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 8d 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.
allowed-tools: Bash(playwright-cli:*), Bash(docker compose:*), Bash(lsof:*), Bash(curl:*), Bash(mkdir:*), Bash(date:*), Read, Write How it starts
The opening of the file, as written. The whole thing — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hands-On Testing with playwright-cli
Perform manual browser-based testing of a web application and produce a structured test report with screenshots and console output.
Workflow
Phase 1: Environment Setup
1.1 Create the test output directory
Generate a timestamp-based output directory for this test run:
TEST_OUTPUT_DIR="$CLAUDE_PROJECT_DIR/test-output/$(date +%Y%m%d%H%M)"
mkdir -p "$TEST_OUTPUT_DIR"
All screenshots and the report for this run will be saved under this directory.
1.2 Check if the dev server is running
# Check if something is listening on the expected port
lsof -i :3000 -sTCP:LISTEN
# or
curl -s -o /dev/null -w "%{http_code}" http://localhost:3000
1.3 Start the dev server if not running
Detect the project's dev server command from project files (compose.yml, package.json, Makefile, etc.) and start it in the background.
# Example: Docker Compose project
docker compose up -d
# Example: Node.js project
# npm run dev &
Wait for the server to become ready:
# Poll until the server responds
for i in $(seq 1 30); do
curl -s -o /dev/null -w "%{http_code}" http://localhost:3000 | grep -q "200" && break
sleep 1
done
Phase 2: Browser Session
2.1 Open the browser and navigate
playwright-cli open http://localhost:3000
Or navigate to a specific page to test:
playwright-cli open http://localhost:3000/path/to/test
2.2 Take a snapshot to understand the page structure
playwright-cli snapshot
Use the snapshot output to identify element refs (e.g., e1, e5, e12) for subsequent interactions.
2.3 Perform test actions
Interact with the page based on the test scenario. Common actions:
# Click elements
playwright-cli click e3
# Fill form fields
playwright-cli fill e5 "test input"
# Type text (simulates keystrokes)
playwright-cli type "search query"
# Press keys
playwright-cli press Enter
# Select dropdown options
playwright-cli select e9 "option-value"
# Check/uncheck checkboxes
playwright-cli check e12
playwright-cli uncheck e12
# Hover
playwright-cli hover e4
# Navigate
playwright-cli goto http://localhost:3000/other-page
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.
- 8d ago First seen · 259 lines · 69 tokens per session scan A 1e67c53b301e
hands-on-test is a skill published in the GitHub repository ktnyt/cclsp (673 stars, last pushed 6mo ago), licensed MIT. It adds 69 tokens to every session and 1,713 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-30.
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…
browser-automation
This skill should be used when the user asks about browser automation, testing web pages, extracting content, filling forms, taking screenshots, or monitoring console/network activity. Activates for E2E testing, form automation, browsing tasks, or debugging web applications.
qa-use
E2E testing and browser automation with qa-use CLI. Use when the user needs to run tests, verify features, automate browser interactions, or debug test failures.
playwright-cli
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
argus
Argus AI-powered QA harness — Chrome DevTools MCP reference for browser automation, accessibility, performance, security, and debugging.