AI agents browsing the web have a problem: they read everything — cookie banners, hidden instructions, dark patterns — and can't tell real content from a trap. Agent Browser Shield sits between your agent and the web, stripping prompt injections, masking PII, removing dark patterns, and filtering page noise that burns tokens. Free, source-available, works with browser-use and Browserbase.
Hey PH! 👋 Britt from PixieBrix here.
We've been building browser tooling for enterprise teams for years, and when we started seeing AI agents get deployed at scale to browse the web, we noticed a gap: agents have zero protection from the stuff (most) humans have learned to watch out for.
Prompt injection is OWASP's #1 AI security threat — and it's trivially easy to embed hidden instructions in a webpage that your agent will follow without question. On top of that, most pages are full of junk (cookie banners, footers, chat widgets) that your agent reads and pays for in tokens.
Agent Browser Shield is our answer: a free, source-available browser extension that strips all of that before the model sees the page. We built it in the open because this is an evolving problem — new dark patterns, new injection techniques — and no single team can keep up alone.
Would love your feedback on what to build next. And if you're running browser agents in production, let us know what failure modes you've hit because we want to keep building and write better rules to make this even better.
GitHub: https://github.com/pixiebrix/age...
PII masking at the proxy layer is smart - agents leak more than most realize. Is the injection detection rules-based or does it adapt as attack patterns evolve? Static filters tend to fall behind pretty quickly in this space.
The token noise problem is honestly what gets me more than the injection side. Most agent failures I've seen aren't dramatic security breaches, they're just the model losing track of what matters after reading 3 cookie banners and a footer nav in a row.
Quick question though, does the filter run once on initial page load or does it watch for DOM mutations? Asking because a lot of the annoying stuff (cookie popups, chat widgets) gets injected dynamically after the page loads.
If someone is already using a token-efficient agent browser (e.g., DOM-diff / structured extraction approaches) or a containment-focused platform approach, where does Agent Browser Shield still add unique value—and where do you explicitly *not* try to compete?
The prompt-injection angle is obviously important, but the token-noise part is what stood out to me. When using browser agents for research/social workflows, the annoying failure mode is often less "one malicious instruction" and more the agent wasting context on cookie banners, nav, footers, and hidden junk before it reaches the actual page content.
Curious if Agent Browser Shield exposes a diff or trace of what it stripped from the page. That would be really useful for debugging false positives, especially when a page has weird layout or important content that looks like boilerplate.
Congrats on the launch — this feels like one of those unglamorous layers that becomes necessary once browser agents move from demos to real workflows.
About Agent Browser Shield on Product Hunt
“Block prompt inject & cut token costs for AI browser agents”
Agent Browser Shield launched on Product Hunt on June 5th, 2026 and earned 105 upvotes and 12 comments, placing #11 on the daily leaderboard. AI agents browsing the web have a problem: they read everything — cookie banners, hidden instructions, dark patterns — and can't tell real content from a trap. Agent Browser Shield sits between your agent and the web, stripping prompt injections, masking PII, removing dark patterns, and filtering page noise that burns tokens. Free, source-available, works with browser-use and Browserbase.
Agent Browser Shield was featured in Browser Extensions (5.3k followers), Open Source (68.5k followers), Artificial Intelligence (471k followers) and GitHub (41.3k followers) on Product Hunt. Together, these topics include over 137.6k products, making this a competitive space to launch in.
Who hunted Agent Browser Shield?
Agent Browser Shield was hunted by Brittany Joiner {Britt the Builder}. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Agent Browser Shield stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Brittany Joiner {Britt the Builder}