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 korbinjoe/TeemAI --skill ui-change-verificationgit clone --depth 1 https://github.com/korbinjoe/TeemAIWrote 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/korbinjoe/teemai/ui-change-verification)<a href="https://agentmods.dev/skills/korbinjoe/teemai/ui-change-verification"><img src="https://agentmods.dev/badge/skills/korbinjoe/teemai/ui-change-verification/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.
<a href="https://agentmods.dev/skills/korbinjoe/teemai/ui-change-verification"><img src="https://agentmods.dev/badge/skills/korbinjoe/teemai/ui-change-verification.svg" alt="Reviewed on agentmods" width="80" 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.00060 | $0.00510 |
| Opus 5 | $0.00030 | $0.00255 |
| Sonnet 5 | $0.00012 | $0.00102 |
| Haiku 4.5 | $0.00006 | $0.00051 |
Grade A, and why
ui-change-verification 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 9d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI Change Verification
Use this skill after every substantial UI-impacting change before reporting the work complete.
When to use
- Frontend components, hooks, layout, routing, keyboard/focus behavior, or visual states changed.
- Backend changes alter WebSocket/API behavior consumed by the UI.
- Terminal, canvas, editor, file tree, chat, mission, or workspace surfaces are affected.
- A bug report describes behavior visible in the app.
When not to use
- Pure documentation changes.
- Pure backend changes with no user-facing UI/API behavior.
- Fast syntax/test-only edits where the affected UI was already verified in the same task and no UI behavior changed afterward.
Workflow
- Identify the changed user workflow and write 2-5 concrete UI assertions.
- Start or reuse the app dev server. Prefer the project’s configured ports.
- Open the app in a browser with Playwright or
playwright-cli. - Navigate to the affected surface using real app routes and existing data when possible.
- Exercise the workflow directly: click, type, toggle, resize, or wait for WebSocket events as the user would.
- Capture evidence using snapshot, screenshots, DOM assertions, console errors, and network/WebSocket observations as appropriate.
- Fix issues found during verification and rerun the relevant UI checks.
- Report the verification method, URL, assertions checked, and any limits.
Minimum expectations
- Verify at least one desktop viewport for every substantial UI change.
- Verify mobile or narrow viewport when layout responsiveness was changed.
- Check browser console errors for the verified page.
- For terminal/canvas/editor surfaces, assert the rendered container is nonblank and has usable dimensions.
- For WebSocket-driven UI, verify both the event path and visible UI result when feasible.
- Do not mark UI-impacting work complete based only on unit tests.
Output format
Include a short verification section in the final answer:
UI verification:
- URL:
- Method:
- Checked:
- Limits:
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.
- 9d ago First seen · 68 lines · 60 tokens per session scan A 17d8d9ff9d57
ui-change-verification is a skill published in the GitHub repository korbinjoe/TeemAI (2 stars, last pushed 2mo ago), licensed MIT. It adds 60 tokens to every session and 510 once invoked, about $0.0003 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
frontman-agent-usage
Use this skill when an agent needs to explain or operate Frontman's browser-aware frontend coding workflow.
web-verify
Look at your OWN front-end change before claiming it works -- navigate the loopback URL of a dev server or pod you started, screenshot the surface you changed, read the image to judge it, and embed it in chat. Three capture backends: playwright-cli (the session the dashboard Browser panel shows), the agent-browser CLI…
crxjs
CRXJS Chrome extension development — true HMR for popup, options, content scripts, side panels, manifest-driven builds, dynamic content script imports (?script, ?script&module), and defineManifest for type-safe manifests. Uses Vite as its build tool. Use when the user mentions CRXJS, crxjs, @crxjs/vite-plugin…
chrome-extension
Use when building or shipping a Manifest V3 browser extension and hitting its quirks — service worker dying and losing state, permission warnings, a Chrome Web Store rejection, content-script/worker/popup messaging, or an MV2-to-V3 migration. NOT a generic web app (that is nextjs), NOT a desktop shell (that is…
aster-ui-demo
How to demo UI work the way Claude does it, never with throwaway HTML mockups. Build the change in the real webview, verify it in the browser harness, open the live dev server for the user to click through, and run the real test suites. Use when the user asks for a demo, a preview, or "let me see" any UI change in the…
azure-maps
Expert knowledge for Azure Maps development including best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, and integrations & coding patterns. Use when using web/REST/Power BI SDKs, geocoding/routing/weather APIs, tiles/rendering, or multi-stop route optimization…