Proma is a local-first AI desktop application that combines multi-model chat, general-purpose agents, workspaces, skills, MCP servers, remote bots, and shared memory. People use it as a workspace for personal workflows, letting agents handle files, browser tasks, long-running jobs, and collaborative subtasks while storing sessions and configuration locally.
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 proma-ai/Proma --skill in-app-browsergit clone --depth 1 https://github.com/proma-ai/PromaWrote 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/proma-ai/proma/in-app-browser)<a href="https://agentmods.dev/skills/proma-ai/proma/in-app-browser"><img src="https://agentmods.dev/badge/skills/proma-ai/proma/in-app-browser/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/proma-ai/proma/in-app-browser"><img src="https://agentmods.dev/badge/skills/proma-ai/proma/in-app-browser.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.00170 | $0.03171 |
| Opus 5.5 | $0.00068 | $0.01268 |
| Sonnet 5.5 | $0.00034 | $0.00634 |
| Haiku 4.5 | $0.00017 | $0.00317 |
Grade A, and why
in-app-browser 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 2mo 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 2mo ago First seen · 88 lines · 170 tokens per session scan A 5a38a1c4c0e0
in-app-browser is a skill published in the GitHub repository proma-ai/Proma (2,235 stars, last pushed 1mo ago), licensed AGPL-3.0. It adds 170 tokens to every session and 3,171 once invoked, about $0.0007 per session on Opus 5.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
computer-use
Control desktop applications through Lume Computer Use.
In-App 浏览器操作
A workflow for operating Lume's built-in web browser through page snapshots and semantic actions such as clicking, typing, selecting, uploading, and downloading. It also covers tabs, scrolling, screenshots, dialogs, and script-based fallback actions.
browser
Control pages in Lume's shared persistent in-app browser profile through built-in browser tools.
chrome-browser
Read this skill before the first step that uses Claude in Chrome, the browser extension whose tools are named mcpclaude-in-chrome (also called Chrome, the browser extension, or the external browser) and which acts in the person's real Chrome with their own sign-ins; before those tools are turned on there may be a…
chrome-devtools
Uses Chrome DevTools via MCP for efficient debugging, troubleshooting and browser automation. Use when debugging web pages, automating browser interactions, analyzing performance, or inspecting network requests. This skill does not apply to --slim mode (MCP configuration).
web-gui-tester
Use the browser automation tooling available in the session to test web frontends interactively in a purely GUI-based, black-box manner: simulate real user clicks, text input, scrolling, and other actions; use screenshots for visual verification and read-only DOM inspection for cross-validation; and produce a final…