Testing content-blind sponsored perks for AI coding sessions

barney wohl — Thu, 18 Jun 2026 04:19:31 +0000

I’m testing a small CLI called BuilderPerks.

It adds optional sponsored devtool perks to AI coding sessions, but with one hard constraint: it should be content-blind.

That means prompts, code, file paths, command output, terminal transcripts, secrets, and personal data are not sent. The product uses broad stack keywords/categories only.

Try the proof block first:

npx -y builderperks@latest proof

If that trust story makes sense, install for Codex:

npx -y builderperks@latest install codex --verify
npx -y builderperks@latest support-proof

I’m also running a small fixed beta feedback bounty for the first 25 real AI-coding builders: USD 5 for a proof screenshot, plus USD 10 for a second session and support-proof. This is not ad revenue, passive income, settled cash, or guaranteed earnings.

Public scoreboard: https://builderperks.netlify.app/scoreboard.html

The question I’m trying to answer: can a sponsored devtool offer be acceptable in an AI-coding workflow if it is labeled, optional, terminal-first, and content-blind?

DEV Community: barney wohl

Testing content-blind sponsored perks for AI coding sessions