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 leeguooooo/chrome-use --skill slackgit clone --depth 1 https://github.com/leeguooooo/chrome-useWrote 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/leeguooooo/chrome-use/slack)<a href="https://agentmods.dev/skills/leeguooooo/chrome-use/slack"><img src="https://agentmods.dev/badge/skills/leeguooooo/chrome-use/slack/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/leeguooooo/chrome-use/slack"><img src="https://agentmods.dev/badge/skills/leeguooooo/chrome-use/slack.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.00088 | $0.01932 |
| Opus 5.5 | $0.00035 | $0.00773 |
| Sonnet 5.5 | $0.00018 | $0.00386 |
| Haiku 4.5 | $0.00009 | $0.00193 |
Grade A, and why
slack 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 8d 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 — 289 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Slack Automation
Interact with Slack workspaces to check messages, extract data, and automate common tasks.
Quick Start
Connect to an existing Slack browser session or open Slack:
# Connect to existing session on port 9222 (typical for already-open Slack)
chrome-use connect 9222
# Or open Slack if not already running
chrome-use open https://app.slack.com
Then take a snapshot to see what's available:
chrome-use snapshot -i
Core Workflow
- Connect/Navigate: Open or connect to Slack
- Snapshot: Get interactive elements with refs (
@e1,@e2, etc.) - Navigate: Click tabs, expand sections, or navigate to specific channels
- Extract/Interact: Read data or perform actions
- Screenshot: Capture evidence of findings
# Example: Check unread channels
chrome-use connect 9222
chrome-use snapshot -i
# Look for "More unreads" button
chrome-use click @e21 # Ref for "More unreads" button
chrome-use screenshot slack-unreads.png
Common Tasks
Checking Unread Messages
# Connect to Slack
chrome-use connect 9222
# Take snapshot to locate unreads button
chrome-use snapshot -i
# Look for:
# - "More unreads" button (usually near top of sidebar)
# - "Unreads" toggle in Activity tab (shows unread count)
# - Channel names with badges/bold text indicating unreads
# Navigate to Activity tab to see all unreads in one view
chrome-use click @e14 # Activity tab (ref may vary)
chrome-use wait 1000
chrome-use screenshot activity-unreads.png
# Or check DMs tab
chrome-use click @e13 # DMs tab
chrome-use screenshot dms.png
# Or expand "More unreads" in sidebar
chrome-use click @e21 # More unreads button
chrome-use wait 500
chrome-use screenshot expanded-unreads.png
Navigating to a Channel
# Search for channel in sidebar or by name
chrome-use snapshot -i
# Look for channel name in the list (e.g., "engineering", "product-design")
# Click on the channel treeitem ref
chrome-use click @e94 # Example: engineering channel ref
chrome-use wait --load networkidle
chrome-use screenshot channel.png
What ships with it
2 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.
- 8d ago Changed 93dc25ab8505
- 1mo ago First seen · 289 lines · 88 tokens per session scan A 2c5475d3d806
slack is a skill published in the GitHub repository leeguooooo/chrome-use (202 stars, last pushed yesterday), licensed Apache-2.0. It adds 88 tokens to every session and 1,932 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. It comes from a forked repository.
Other skills, from other repositories
surf
Control Chrome browser via CLI for testing, automation, and debugging. Use when the user needs browser automation, screenshots, form filling, page inspection, network/CPU emulation, DevTools streaming, or AI queries via ChatGPT/Gemini/Perplexity/Grok/AI Studio.
Agent Browser Automation
Fast Rust-based headless browser automation CLI with Node.js fallback for AI agents, featuring navigation, clicking, typing, snapshots, and structured commands optimized for agent workflows.
Browser-Use Automation
CLI tool for persistent browser automation with multi-session support, featuring Chromium/Real/Remote browser modes, cookie management, JavaScript execution, and long-running automation workflows.
cursor-browser
Drive Cursor IDE's built-in Browser Tab via cursor-browser-cli. Navigate, ref snapshots, click/type/fill/scroll/select-option by ref, wait-for, lock, screenshot, console/network/inspect. For Grok Build, Claude Code, Codex in Cursor terminal. Triggers: Cursor browser, Browser Tab, /cursor-browser, snapshot, under the…
wbrowser
Use when a task needs a browser that is already signed in — reading a dashboard, checking a web app, filling a form, taking a screenshot of a real page, or debugging a site's console. Drives a real Chrome window the user signed into by hand, so no re-login and no API keys. Do not guess selectors; run wb read first and…
ultimate-playwright
Browser automation via ultimate-playwright-mcp. Use when the agent needs to control a shared Chrome browser — open tabs, navigate, click, type, fill forms, take snapshots. Handles multi-user tab group isolation so multiple sessions can share one browser without interference. Use for web browsing, scraping, form…