Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add gettalon/talon-plugins/plugin install talonWrote 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/commands/gettalon/talon-plugins/web-setup)<a href="https://agentmods.dev/commands/gettalon/talon-plugins/web-setup"><img src="https://agentmods.dev/badge/commands/gettalon/talon-plugins/web-setup/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/commands/gettalon/talon-plugins/web-setup"><img src="https://agentmods.dev/badge/commands/gettalon/talon-plugins/web-setup.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00035 | $0.00861 |
| Opus 5.5 | $0.00014 | $0.00344 |
| Sonnet 5.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 1mo 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 — 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.
- 1mo ago First seen · 101 lines · 35 tokens per session scan A b9e235c77325
web-setup is a command published in the GitHub repository gettalon/talon-plugins (6 stars, last pushed 6mo ago), licensed MIT. It adds 35 tokens to every session and 861 once invoked, about $0.0001 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-31.
Other commands, from other repositories
qa
Dispatch a verifiable browser task to the qa-tester subagent. Use for regression checks, smoke tests, and any task with a clean pass/fail outcome. Supports an EXHAUSTIVE mode that verifies every control behind an honesty gate.
playbook
Manage Mochi playbooks (list, show, run, delete). Plays through the browser MCP tools.
unschedule-playbook
Cancel a scheduled playbook routine.
check-browser
Use Real Browser MCP to check what's currently showing in my browser.
checkpoint
Write a new link in the continuum chain summarizing decisions/changes since the last link.
design-qa
Agent-driven design QA — walk the running app, judge design/UX, and drop a Comment-Mode comment on every issue (visible to the human as pins). Then read the session back and fix everything in bulk. Optional focus argument steers the pass.