agentmods.dev

agent-browser-issue

A process for reporting reusable problems in browser automation tools to GitHub. It focuses on tool failures such as blocked clicks, dropdowns, file uploads, focus traps, or similar actions.

In plain words
What is it for?
Use it to record the URL, attempted action, expected and actual results, and steps to reproduce a browser-automation limitation.
Why use it?
It turns a vague automation failure into a short, repeatable report that maintainers can investigate, while separating tool problems from website, login, or one-off issues.

Cursor rule for Codex

240 12d ago A scan 52 tokens original MIT
View the source file udecode/plate-playground-template
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 rules/udecode/plate-playground-template/agent-browser-issue
Clone the repo
git clone --depth 1 https://github.com/udecode/plate-playground-template

Made for: Codex.

Per session 52 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 318 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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 $0.00052 $0.00318
Opus 5 $0.00026 $0.00159
Sonnet 5 $0.00010 $0.00064
Haiku 4.5 $0.00005 $0.00032

Measured 2d ago against content hash 6717bcbcb296, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

agent-browser-issue 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.agents/rules/agent-browser-issue.mdc · 66 lines

What it actually says

Agent Browser Issue

Handle $ARGUMENTS.

Use this only for likely reusable agent/browser tooling bugs. Do not use it for:

  • auth or SSO gates
  • manual human gates
  • product bugs on the site itself
  • one-off flaky noise with no minimal repro

Collect

Capture only the minimum:

  • page or URL
  • action attempted
  • exact block
  • expected vs actual
  • minimal repro
  • screenshot only if it adds signal

Issue

Open a GitHub issue with:

  • a short title focused on the browser/tool failure
  • label agent:browser
  • concise body

Body shape:

## URL
<url>

## Action
<what the agent tried>

## Block
<what failed>

## Expected
<what should have happened>

## Actual
<what happened instead>

## Repro
1. ...
2. ...
3. ...

After

  • if the browser/tool failure exposes a user-action parity gap, load agent-native-reviewer and note that gap in the issue
  • link the issue in the task caveat or handoff
  • keep moving if the product task is still otherwise fixable
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. 2d ago First seen · 66 lines · 52 tokens per session scan A 6717bcbcb296

Subscribe to this mod's changes

agent-browser-issue is a cursor rule published in the GitHub repository udecode/plate-playground-template (240 stars, last pushed 12d ago), licensed MIT. It adds 52 tokens to every session and 318 once invoked, about $0.0003 per session on Opus 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-30.

Browser automationDebuggingeditornextjsplateradix-uishadcn-uislate
Related

Other cursor rules, from other repositories

dev-browser

Fallback browser automation with persistent Chrome state. Use only when Browser Use is unavailable or blocked.

udecode/plate-template · 18 tokens

browser-debug-setup

One-time setup for a persistent debug browser on 127.0.0.1:9222 for dev-browser --connect. Use when browser work is needed but no reusable debug browser is running yet.

udecode/plate-template · 43 tokens

agent-browser-issue

Open a concise GitHub follow-up for reusable browser-use limitations. Use when browser automation is blocked by a likely tool-side issue that is worth fixing separately, especially for clicks, dropdowns, file inputs, focus traps, or other repeatable agent/browser failures.

udecode/plate-template · 52 tokens

testing

Cursor rule "testing" from udecode/plate-template, covering testing goal, core rules, seam selection, fixtures and assertions and quick reference.

udecode/plate-template · 315 tokens

components

React component architecture for creating composable, accessible components with data attributes. Use when creating/updating composable components, not for higher-level feature/page components.

udecode/plate-template · 31 tokens

react

React patterns with destructured props, compiler optimization, Effects, and Tailwind v4 syntax. ALWAYS use when using React.

udecode/plate-template · 25 tokens