setup

setup is a command for Claude Code from lttr/claude-marketplace. It costs 0 tokens per session (565 once invoked), scanned B, original, MIT.

A setup command for a browser-tools add-on. It installs its dependencies, prepares the tool scripts, and creates command shortcuts that can be used from the terminal.

In plain words
What is it for?
Use it when setting up browser automation commands for starting a browser, opening pages, running browser code, selecting elements, reading cookies, or taking screenshots.
Why use it?
It handles the installation steps required before the browser tools can be used. The shortcuts make the commands easier to run.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths.

Part of the browser-tools plugin — 1 skill, 1 command shipped together

Install

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.

agentmods
npx agentmods add commands/lttr/claude-marketplace/setup
Clone the repo
git clone --depth 1 https://github.com/lttr/claude-marketplace

Made for: Claude Code.

Or install browser-tools, the plugin that ships this one along with the rest of its 1 skill, 1 command.

Wrote 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.

agentmods badge for setup

README.md
[![agentmods](https://agentmods.dev/badge/commands/lttr/claude-marketplace/setup.svg)](https://agentmods.dev/commands/lttr/claude-marketplace/setup)
Your own site
<a href="https://agentmods.dev/commands/lttr/claude-marketplace/setup"><img src="https://agentmods.dev/badge/commands/lttr/claude-marketplace/setup.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 565 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00565
Opus 5 $0.00000 $0.00282
Sonnet 5 $0.00000 $0.00113
Haiku 4.5 $0.00000 $0.00056

Measured 5d ago against content hash 97f25afff048, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade B, and why

setup scanned grade B 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 5d 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

SCRIPTS_DIR=$(find ~/.claude/plugins -type d -path "*/browser-tools/skills/browser-tools/scripts" 2>/dev/null | head -1)
_archived/browser-tools/commands/setup.md · 93 lines

What it actually says

Set up browser-tools plugin by installing dependencies and creating global symlinks.

Execution steps:

Step 1: Find the plugin scripts directory

Locate the browser-tools scripts directory (search in ~/.claude/plugins for browser-tools plugin):

SCRIPTS_DIR=$(find ~/.claude/plugins -type d -path "*/browser-tools/skills/browser-tools/scripts" 2>/dev/null | head -1)

Verify it was found:

echo "Found scripts at: $SCRIPTS_DIR"

Step 2: Install dependencies

cd "$SCRIPTS_DIR" && pnpm install

Step 3: Create ~/bin directory

mkdir -p ~/bin

Step 4: Make scripts executable

chmod +x "$SCRIPTS_DIR"/browser-*.js

Step 5: Create symlinks (WITHOUT .js extension)

IMPORTANT: Symlink names should NOT have .js extension:

ln -sf "$SCRIPTS_DIR/browser-start.js" ~/bin/browser-start
ln -sf "$SCRIPTS_DIR/browser-nav.js" ~/bin/browser-nav
ln -sf "$SCRIPTS_DIR/browser-eval.js" ~/bin/browser-eval
ln -sf "$SCRIPTS_DIR/browser-screenshot.js" ~/bin/browser-screenshot
ln -sf "$SCRIPTS_DIR/browser-pick.js" ~/bin/browser-pick
ln -sf "$SCRIPTS_DIR/browser-cookies.js" ~/bin/browser-cookies
ln -sf "$SCRIPTS_DIR/browser-console.js" ~/bin/browser-console

Step 6: Verify PATH

Check if ~/bin is in PATH:

case "$PATH" in
  *"$HOME/bin"*) echo "✓ ~/bin is in PATH" ;;
  *) echo "⚠ WARNING: Add ~/bin to PATH in your shell profile" ;;
esac

Summary

After completion, report:

  • Dependencies installed: ✓
  • Symlinks created: browser-start, browser-nav, browser-eval, browser-screenshot, browser-pick, browser-cookies, browser-console
  • PATH status: (OK or needs manual addition)

The browser-tools skill is now ready! Ask me to test web pages, take screenshots, or interact with browsers.

Changes

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.

  1. 5d ago First seen · 93 lines · 0 tokens per session scan B 97f25afff048

Subscribe to this mod's changes

setup is a command published in the GitHub repository lttr/claude-marketplace (2 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 565 tokens. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.