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 agentmods add skills/jonnyton/tinyassets/ui-testnpx skills add Jonnyton/TinyAssets --skill ui-testgit clone --depth 1 https://github.com/Jonnyton/TinyAssetsWhat 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 | $0.00092 | $0.09116 |
| Opus 5 | $0.00046 | $0.04558 |
| Sonnet 5 | $0.00018 | $0.01823 |
| Haiku 4.5 | $0.00009 | $0.00912 |
Grade A, and why
ui-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 2d 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.
3. **Corroborate through a second channel.** An unauthenticated `curl` against the same live endpoint How it starts
The opening of the file, as written. The whole thing — 503 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ui-test
You simulate a real person chatting with Claude.ai or ChatGPT on their phone or laptop, using the TinyAssets MCP connector at https://tinyassets.io/mcp (the canonical URL installed by users). You do not call the MCP directly. You do not parse DOM metadata that a human user cannot see. You type into the chat box. You read the rendered response. You log what happened.
The human host is watching the browser tab. Your job is to look like a naive, curious user — one who does not know tool names, action parameters, or anything about the system's internals. If the chatbot doesn't understand you, that's a finding, not a problem to route around.
Driver routes
- Codex / OpenAI-family route: use any harness-supported browser control path that keeps the same live chatbot tab visible to the host: Codex in-app Browser, the Chrome extension/plugin, CDP or a CLI browser driver, or an equivalent visible route. Open or continue
https://claude.ai/by default; ChatGPT Developer Mode is also valid when its TinyAssets connector is installed. If one driver is unavailable, try another host-visible driver before declaring a blocker. - Claude Code route: use the visible Chrome profile through
scripts/claude_chat.py. This remains the default route for Claude team user-sim. Host-login Claude.ai access is not the proof requirement; Claude.ai is valid when a real browser session can use the TinyAssets connector. - Anthropic / Cowork ChatGPT route: when an Anthropic-family driver has browser or computer control, use ChatGPT when Developer Mode is enabled and the TinyAssets connector is added/visible in that same session. Do not verify in an isolated browser profile unless the host explicitly says that profile is the user-installed connector state. Claude Code on Windows can drive this route via
scripts/chatgpt_chat.py(sibling ofclaude_chat.py, same CDP atlocalhost:9222, reuses the Chrome profile).
Proof standard
The verification target is a rendered chatbot conversation using the live installed connector. Claude.ai, ChatGPT Developer Mode, and future chatbot clients are all acceptable when the host can watch the same live tab, the tester can see the connector in the browser, type a normal user prompt, and observe the chatbot's rendered answer or tool-use result. The browser-control transport is an implementation detail, not part of the proof contract. Browser automation, screenshots, DOM snapshots, direct tests, and public canaries can help navigate or gather supporting evidence; they do not replace final rendered chatbot proof.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 503 lines · 92 tokens per session scan A db8118b7ba37
ui-test is a skill published in the GitHub repository Jonnyton/TinyAssets (1 stars, last pushed 2d ago), licensed MIT. It adds 92 tokens to every session and 9,116 once invoked, about $0.0005 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-31.
Other skills, from other repositories
browse
Fast headless browser for QA testing and site dogfooding. (gstack).
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
e2e-deployment-skill
Use this deployment skill to verify shared skills load during Playwright startup.
launch
Launch Code OSS (VS Code from sources) into an isolated throwaway profile with unique debug ports so you can drive it with @playwright/cli AND attach a Node debugger via dap-cli in the same session. Use when working on VS Code itself and you want to interact with the running workbench, automate chat or UI flows, test…
playwright-screen-recording
Record browser test videos with Playwright for PR review and bug fix verification.
playwright-migration
Step-by-step migration guides for moving to Playwright from Cypress or Selenium/WebDriver — command mappings, architecture changes, and incremental adoption strategies.