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/ariffazil/arifos/browsernpx skills add ariffazil/arifOS --skill browsergit clone --depth 1 https://github.com/ariffazil/arifOSWrote 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/ariffazil/arifos/browser)<a href="https://agentmods.dev/skills/ariffazil/arifos/browser"><img src="https://agentmods.dev/badge/skills/ariffazil/arifos/browser.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 | $0.00020 | $0.01489 |
| Opus 5 | $0.00010 | $0.00745 |
| Sonnet 5 | $0.00004 | $0.00298 |
| Haiku 4.5 | $0.00002 | $0.00149 |
Grade A, and why
browser 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 4d 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.
curl -s -X POST http://headless_browser:3000/screenshot \ 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.
- 4d ago First seen · 173 lines · 20 tokens per session scan A 8051b5dd4401
browser is a skill published in the GitHub repository ariffazil/arifOS (51 stars, last pushed today), licensed AGPL-3.0. It adds 20 tokens to every session and 1,489 once invoked, about $0.0001 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-30.
Other skills, from other repositories
code-browser
The primary tool for code-navigation questions in ANY language (frontend or backend) — walk the structural graph from an entry point (page, route, handler, command, main) down through imports to the IO boundary (network call, query, file read). Use this skill, in preference to the Explore agent or global grep…
document
Workflow Phase 10 — orchestrator for documentation work. Surveys the diff, routes any page on a documentation surface through technical-writer, standalone technical reference through the documentation skill, tutorials through technical-tutorials, and all other prose body work (inline docs, README updates, user-facing…
intake
Draft a Workflow Phase 1 intake document capturing a new request — the problem, the desired outcome, constraints, and testable acceptance criteria. Use when a user brings a new feature, change, or investigation that doesn't yet have a spec. The output lives at docs/intake/ .md and feeds /scout, /research, and /spec…
brd
Draft a Business Requirements Document (BRD) for cross-functional or stakeholder-heavy work that needs more structure than an intake. Use after /intake when the request spans multiple systems/teams, carries regulatory weight, or needs formal sign-off. Output lives at docs/brd/ .md.
agent-browser
Core agent-browser usage guide. Read this before running any agent-browser commands. Covers the snapshot-and-ref workflow, navigating pages, interacting with elements (click, fill, type, select), extracting text and data, taking screenshots, managing tabs, handling forms and auth, waiting for content, running multiple…
documentation
Write and maintain technical documentation. Trigger with "write docs for", "document this", "create a README", "write a runbook", "onboarding guide", or when the user needs help with any form of technical writing — API docs, architecture docs, or operational runbooks.