Skip to content

fix: escape ! in markdown code block to avoid bash permission check false positive #719

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Cerdore wants to merge 2 commits into
base: main
Choose a base branch
from
Open

fix: escape ! in markdown code block to avoid bash permission check false positive #719

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5cbf3b3
fix: escape `!` in markdown code block to avoid bash permission check…
Cerdore Mar 11, 2026
104d1e8
Apply suggestion from @vercel[bot]
Cerdore Mar 11, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions skills/agent-browser/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -113,7 +113,7 @@ agent-browser diff url <url1> <url2> --selector "#main" # Scope to element
agent-browser open https://example.com/signup
agent-browser snapshot -i
agent-browser fill @e1 "Jane Doe"
agent-browser fill @e2 "jane@example.com"
agent-browser fill @e2 "jane@example.com"Control+f
agent-browser select @e3 "California"
agent-browser check @e4
agent-browser click @e5
Expand Down Expand Up @@ -482,7 +482,7 @@ EVALEOF
agent-browser eval -b "$(echo -n 'Array.from(document.querySelectorAll("a")).map(a => a.href)' | base64)"
```

**Why this matters:** When the shell processes your command, inner double quotes, `!` characters (history expansion), backticks, and `$()` can all corrupt the JavaScript before it reaches agent-browser. The `--stdin` and `-b` flags bypass shell interpretation entirely.
**Why this matters:** When the shell processes your command, inner double quotes, `&#33;` characters (history expansion), backticks, and `$()` can all corrupt the JavaScript before it reaches agent-browser. The `--stdin` and `-b` flags bypass shell interpretation entirely.

**Rules of thumb:**
- Single-line, no nested quotes -> regular `eval 'expression'` with single quotes is fine
Expand Down