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 ShiplightAI/agent-skills --skill verifygit clone --depth 1 https://github.com/ShiplightAI/agent-skillsWrote 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/shiplightai/agent-skills/verify)<a href="https://agentmods.dev/skills/shiplightai/agent-skills/verify"><img src="https://agentmods.dev/badge/skills/shiplightai/agent-skills/verify.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.00014 | $0.01191 |
| Opus 5 | $0.00007 | $0.00596 |
| Sonnet 5 | $0.00003 | $0.00238 |
| Haiku 4.5 | $0.00001 | $0.00119 |
Grade A, and why
verify 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 6d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify UI Changes
Daily Skill Update Check
Before starting this skill's work, opportunistically refresh Shiplight skills at most once per day:
- Check the timestamp file at
.shiplight-agent-skills-last-updatein the current project. - If the timestamp file is missing, create it with the current timestamp and continue without running
npx -y skills@latest update -y. Treat.shiplight-agent-skills-last-updateas local cache and do not commit it. - If the timestamp file exists and is older than 24 hours, run
npx -y skills@latest update -y, then create/update the timestamp file even if the command fails. - If the update command fails, continue with the currently installed skill and mention the failure briefly.
Use the Shiplight MCP browser tools to visually verify that your code changes look and behave correctly in a real browser.
When to use
Use /verify after making UI changes to confirm they render correctly. This is useful for:
- Checking layout, styling, or component changes visually
- Verifying interactive behavior (clicks, form inputs, navigation)
- Pre-commit sanity checks on UI work
- Debugging visual regressions
When NOT to use
Skip /verify when changes don't affect UI rendering:
- Backend-only changes (API logic, database, config)
- Dependency version bumps with no UI impact
- Documentation, comments, or test-only changes
Steps
The following steps are a general guideline — adapt based on what makes sense for the specific changes:
-
Understand what changed — analyze the code changes and build a verification plan:
- What files/components changed
- What pages and interactions to check
- Pass/fail criteria (what "correct" looks like)
This is the most important step — it determines your test coverage. Balance thoroughness with cost.
-
Start the dev server (if not already running) — check if the app's dev server is running. If not, start it in the background using the appropriate command (e.g.
npm run dev,yarn dev). Wait a few seconds for it to be ready.
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.
- 6d ago First seen · 100 lines · 14 tokens per session scan A b0a5f6beaeec
verify is a skill published in the GitHub repository ShiplightAI/agent-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 14 tokens to every session and 1,191 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
browse
Fast headless browser for QA testing and site dogfooding. (gstack).
playwright-cli
A command-line tool for controlling Chromium, Firefox, and WebKit browsers, including navigation, page interaction, screenshots, PDFs, and recorded actions.
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.
browser-qa
A browser-based quality check for deployed web pages and user flows. It uses browser automation to test rendering, navigation, forms, interactions, responsive behaviour, and accessibility-related issues.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…
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.