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/gettalon/talon-plugins/web-setupnpx skills add gettalon/talon-plugins --skill web-setupgit clone --depth 1 https://github.com/gettalon/talon-pluginsWhat 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.00035 | $0.00861 |
| Opus 5 | $0.00017 | $0.00430 |
| Sonnet 5 | $0.00007 | $0.00172 |
| Haiku 4.5 | $0.00003 | $0.00086 |
Grade A, and why
web-setup 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 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.
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.
This is a copy
97% identical to setup — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Browser Control Setup Guide
Help the user set up the Talon Chrome extension so Claude Code can control their browser and chat from Chrome.
Steps
1. Install the Chrome Extension
Run the install script to copy the extension to Downloads:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/install-extension.sh"
This copies the extension to ~/Downloads/talon-browser-control and opens Chrome's extensions page.
2. Load in Chrome
Guide the user through these steps:
- Open Chrome and go to
chrome://extensions - Enable Developer Mode (toggle in the top right)
- Click "Load unpacked"
- Select
~/Downloads/talon-browser-control - The Talon extension icon should appear in the Chrome toolbar
3. Verify Connection
Once loaded, the extension will auto-connect to the MCP server. Verify by running:
browser_control with action: "get_tabs"
If it returns tabs, the connection is working.
4. Enable Chat (Claude Code Channels)
This plugin uses Claude Code's channels feature (research preview, requires v2.1.80+) for two-way chat between the Chrome extension and Claude Code.
Requirements:
- Claude Code v2.1.80 or later
- claude.ai login (Console/API key auth not supported)
- Team/Enterprise orgs must have channels enabled by admin
Start with channels enabled:
Since this is a custom channel (not on the official allowlist yet), use the development flag:
claude --dangerously-load-development-channels plugin:browser-control@gettalon-talon-plugins
You can combine with other channels:
claude --dangerously-load-development-channels plugin:browser-control@gettalon-talon-plugins --channels plugin:telegram@claude-plugins-official
Once started with channels:
- Open the extension's side panel (click the Talon icon or right-click → "Open side panel")
- Type a message — it arrives in Claude Code as a
<channel source="talon-browser">notification - Claude can reply back to the side panel
- Claude's browser tool actions also appear in the side panel in real-time
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 · 101 lines · 35 tokens per session scan A b9e235c77325
web-setup is a skill published in the GitHub repository gettalon/talon-plugins (6 stars, last pushed 5mo ago), licensed MIT. It adds 35 tokens to every session and 861 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to setup, differing in 3 lines, and is treated as a copy.
Other skills, from other repositories
browser
Use this skill when the user says browser, /browser, test in Chrome, inspect a webpage, verify a localhost app, capture screenshots, check console/network errors, run browser QA, or automate browser flows with the Mochi browser MCP.
browse
Use when asked to interact with a web browser — navigate, click, fill forms, take screenshots, run JavaScript, or read page content. Requires the browser-bridge MCP server and Chrome extension.
NanoBanana-PPT-Skills
Skill "NanoBanana-PPT-Skills" from girish6055/NanoBanana-PPT-Skills, covering ppt generator pro - claude code skill, 📋 元数据, ✨ 功能特性, 核心功能 and 新功能 (v2.0).
codex-browser
Control Chrome or Edge via the ChatGPT desktop app's browser bridge (formerly Codex Desktop). 52 MCP tools for tabs, navigation, DOM, input, CDP, network, file upload, dialog handling, and diagnostics.
x402
Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — "just use it" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing…
browser-use
Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work.