agentmods.dev

agentcmd: Command for Claude Code

.claude/commands/use-browser.md

use-browser is a command for Claude Code from jnarowski/agentcmd. It costs 12 tokens per session (699 once invoked), scanned A, original, MIT.

A browser-based feature-checking workflow that logs into an application, follows specified steps, and reports or fixes problems it finds.

In plain words
What is it for?
Use it for end-to-end testing of logged-in features, including capturing screenshots when failures occur and repeating the check after fixes.
Why use it?
It helps verify that a feature works through the user interface rather than relying only on code-level checks.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: positional $N argument.

This is jnarowski/agentcmd's own configuration. It tells Claude Code how to work on agentcmd itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything agentcmd configures →

not rated 18repo 10mo ago A scan 12 tokens original MIT
View source ↗ jnarowski/agentcmd agentcmd.dev
Reuse

Borrowing it

Nothing to install: this file belongs to jnarowski/agentcmd. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/jnarowski/agentcmd/main/.claude/commands/use-browser.md
Clone the repo
git clone --depth 1 https://github.com/jnarowski/agentcmd

Made for: Claude Code.

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 use-browser

README.md
[![agentmods](https://agentmods.dev/badge/commands/jnarowski/agentcmd/use-browser/github.svg)](https://agentmods.dev/commands/jnarowski/agentcmd/use-browser)
Your own site
<a href="https://agentmods.dev/commands/jnarowski/agentcmd/use-browser"><img src="https://agentmods.dev/badge/commands/jnarowski/agentcmd/use-browser/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.

agentmods 80×15 button for use-browser

Your own site · 80×15
<a href="https://agentmods.dev/commands/jnarowski/agentcmd/use-browser"><img src="https://agentmods.dev/badge/commands/jnarowski/agentcmd/use-browser.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 699 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.00012 $0.00699
Opus 5.5 $0.00005 $0.00280
Sonnet 5.5 $0.00002 $0.00140
Haiku 4.5 $0.00001 $0.00070

Measured 2mo ago against content hash daba5c048d0e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

use-browser 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 2mo 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.

.claude/commands/use-browser.md · 97 lines

How it starts

The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Use Browser to Verify Feature

Automates browser testing to verify a feature is working correctly in the application. Logs into the app using test credentials, validates the feature, and iterates on fixes until successful.

Variables

  • $featureSteps: $1 (required) - Description of the feature to verify (e.g., "user can create new projects", "dashboard displays metrics correctly")
  • $testUrl: fetch TEST_URL from env
  • $testUsername: fetch TEST_USERNAME from env
  • $testPassword: fetch TEST_PASSWORD from env

Instructions

  • ALWAYS use Playwright MCP tools for browser automation
  • Log in using credentials from environment variables TEST_USERNAME and TEST_PASSWORD
  • Login URL: $testUrl
  • Test the feature thoroughly based on the description provided
  • If issues are found, fix them and re-test
  • DO NOT finish until the feature is verified as working
  • Take screenshots of failures to help with debugging
  • Report all issues found and fixes applied

Workflow

  1. Authenticate

    • Navigate to $testUrl from environment
    • Fill in username field with $testUsername from environment
    • Fill in password field with $testPassword from environment
    • Submit the login form
    • Verify successful login (check for redirect or dashboard)

  2. Test the Feature

    • Navigate to the relevant page/section for the feature
    • Perform the actions described in $featureSteps
    • Capture any errors, unexpected behavior, or visual issues
    • Take screenshots if verification fails

  3. Iterate on Issues

    • If issues found: a. Document the specific problem b. Identify the root cause (use code search, read relevant files) c. Implement fixes to the codebase d. Return to step 1 (re-authenticate and re-test)
    • Repeat until feature works correctly

  4. Final Verification

    • Run one complete end-to-end test of the feature
    • Verify no console errors or warnings
    • Confirm expected behavior matches requirements
    • Document the successful test result

Read the full file on GitHub · 97 lines

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. 2mo ago First seen · 97 lines · 12 tokens per session scan A daba5c048d0e

Subscribe to this mod's changes

use-browser is a command published in the GitHub repository jnarowski/agentcmd (18 stars, last pushed 10mo ago), licensed MIT. It adds 12 tokens to every session and 699 once invoked, about $0.0000 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-09-01.

Browser automationE2E testingTesting
Related

use-browser compared with commands from other repositories

use-browser next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
use-browserjnarowski/agentcmdCommand1810mo agoMITA12Claude Code
expectyonatangross/orchestkitCommand299yesterdayMITA51Claude Code, Cursor
webapp-testinghamr0/agentic-toolkitCommand236d agoApache-2.0A35Claude Code
amazing-e2e-checkbtspoony/mstar-harnessCommand682d agoMITA29Claude Code
recordMarcosNahuel/antigravity-plugin-ccCommand3226d agoMITA38Claude Code
verify-prdesplega-ai/qa-useCommand291mo agoMITA0Claude Code
auto-verifyInsajin/autopus-adkCommand1111mo agoMITA20Claude Code