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.
npx skills add OKHP3/skillz --skill scoutqa-testgit clone --depth 1 https://github.com/OKHP3/skillzWrote 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/okhp3/skillz/scoutqa-test)<a href="https://agentmods.dev/skills/okhp3/skillz/scoutqa-test"><img src="https://agentmods.dev/badge/skills/okhp3/skillz/scoutqa-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.00093 | $0.03049 |
| Opus 5 | $0.00046 | $0.01524 |
| Sonnet 5 | $0.00019 | $0.00610 |
| Haiku 4.5 | $0.00009 | $0.00305 |
Grade A, and why
scoutqa-test 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 4d 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 — 376 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ScoutQA Testing Skill
Perform AI-powered exploratory testing on web applications using the scoutqa CLI.
Think of ScoutQA as an intelligent testing partner that can autonomously explore, discover issues, and verify features. Delegate testing to multiple parallel ScoutQA executions to maximize coverage while saving time.
When to Use This Skill
Use this skill in two scenarios:
- User requests testing - When the user explicitly asks to test a website or verify functionality
- Proactive verification - After implementing web features, automatically run tests to verify the implementation works correctly
Example proactive usage:
- After implementing a login form → Test the authentication flow
- After adding form validation → Verify validation rules and error handling
- After building a checkout flow → Test the end-to-end purchase process
- After fixing a bug → Verify the fix works and didn't break other features
Best practice: When you finish implementing a web feature, proactively start a ScoutQA test in the background to verify it works while you continue with other tasks.
Running Tests
Testing Workflow
Copy this checklist and track your progress:
Testing Progress:
- Write specific test prompt with clear expectations
- Run scoutqa command in background
- Inform user of execution ID and browser URL
- Extract and analyze results
Step 1: Write specific test prompt
See "Writing Effective Prompts" section below for guidelines.
Step 2: Run scoutqa command
IMPORTANT: Use the Bash tool's timeout parameter (5000ms = 5 seconds) to capture execution details:
When calling the Bash tool, set timeout: 5000 as a parameter:
- This is the Bash tool's built-in timeout parameter in Claude Code (NOT the Unix
timeoutcommand) - After 5 seconds, the Bash tool returns control with a task ID and the process continues running in the background
- This is different from Unix
timeoutwhich kills the process - here the process keeps running - The first 5 seconds capture the execution ID and browser URL from ScoutQA's output
- The test continues running remotely on ScoutQA's infrastructure with the background task
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.
- 4d ago First seen · 376 lines · 93 tokens per session scan A 6c09a43984b0
scoutqa-test is a skill published in the GitHub repository OKHP3/skillz (3 stars, last pushed today), licensed MIT. It adds 93 tokens to every session and 3,049 once invoked, about $0.0005 per session on Opus 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-09-03.
Other skills, from other repositories
agent-browser
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.
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…
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.
devlab-web-visual-ops
A browser-based operations guide for web applications, including single-page apps, micro-frontends, and multi-page sites. It covers observing, navigating, interacting, inspecting, validating, and capturing pages with browser automation and visual fallbacks.
e2e-playwright
Use when writing end-to-end browser tests with Playwright. Covers resilient locators, auto-waiting, network interception, authentication reuse, parallelization, and eliminating flakiness.
web-app-testing
Use when testing a web application interactively — verifying a feature, reproducing a bug, or checking a flow in a real browser. Covers systematic exploration, console and network inspection, and reporting what you find.