AIRI is a self-hosted virtual AI companion that gives an AI character a voice, visual presence, memory, and the ability to interact with games and coding activity. People use it as a personal digital companion on the web, macOS, or Windows, including for voice chat and gameplay. The catalogue add-ons provide workflows for working with the AIRI project.
Borrowing it
Nothing to install: this file belongs to moeru-ai/airi. 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/moeru-ai/airi/main/.agents/skills/use-agent-browser-with-input-file/SKILL.mdgit clone --depth 1 https://github.com/moeru-ai/airiWrote 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/moeru-ai/airi/use-agent-browser-with-input-file)<a href="https://agentmods.dev/skills/moeru-ai/airi/use-agent-browser-with-input-file"><img src="https://agentmods.dev/badge/skills/moeru-ai/airi/use-agent-browser-with-input-file/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/moeru-ai/airi/use-agent-browser-with-input-file"><img src="https://agentmods.dev/badge/skills/moeru-ai/airi/use-agent-browser-with-input-file.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00504 |
| Opus 5 | $0.00030 | $0.00252 |
| Sonnet 5 | $0.00012 | $0.00101 |
| Haiku 4.5 | $0.00006 | $0.00050 |
Grade A, and why
use-agent-browser-with-input-file 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 11d 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 — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Use Agent Browser with an Input File
Invoke $agent-browser first and run agent-browser skills get agent-browser --full before issuing browser commands. For Electron, also invoke $agent-browser-electron and attach to the intended renderer target.
Resolve the input file to an absolute path and verify that it exists. Then inspect the DOM before choosing an upload method:
- For an attached
input[type="file"], including a visually hidden input, read references/attached-input.md. - For an input created on demand or kept detached from the DOM by application code, read references/detached-input.md.
- For a native file chooser or a flow where no HTML input can be addressed, read references/native-file-chooser.md.
- For evidence requirements after the file is assigned, read references/verify-upload.md.
Workflow
- Open the target route and inspect
snapshot -iand the DOM around the upload control. - Determine whether the input already exists, appears after interaction, remains detached, or delegates to a native picker.
- Apply the matching reference without changing application source code.
- Re-snapshot after each interaction because element refs can become stale.
- Verify application-specific processing, persistence, and final output separately.
- Inspect browser errors and relevant console output.
- Restore any temporary browser-session instrumentation and close the session.
Keep the same --session and, for Electron, --cdp <port> options on every command. When Electron exposes several targets, use the discovery process from $agent-browser-electron and confirm the active target URL before uploading.
Handoff to Vishot
Use Agent Browser to discover inputs, diagnose selectors, and prove the interaction. Once the flow is stable, encode it in a Playwright-backed Vishot scenario with $use-vishot-with-input-file when deterministic visual evidence is required.
What ships with it
5 files 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.
- 11d ago First seen · 34 lines · 60 tokens per session scan A 555bedc8d4a6
use-agent-browser-with-input-file is a skill published in the GitHub repository moeru-ai/airi (49,010 stars, last pushed today), licensed MIT. It adds 60 tokens to every session and 504 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-30.
Other skills, from other repositories
browse
Drive a real browser through Aside: open a page, read it, click through a flow, take screenshots, check console errors. (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.
create-verification-skill
Create a repo-local verification skill and exhaustive feature map for driving a real app through its UI, CLI, or API. Use for "create a verification skill", "make a verify skill for this repo", or "document how agents can verify this app".
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…