darken-page-except-video-player
The dark mode the site never shipped, on the one page you watch.
Live tools
Create
your
own
agent
tool,
for
the
site
you
made
it
on
Ask for something the built-in tools cannot do. Read the code the agent writes, keep it, and it becomes a tool of your own that runs by name.
How one gets made
Four steps, and you only do two of them
-
01
Ask for the thing no tool does
Flip the Live tool switch and say what you want. Seek a video, read a canvas, archive every row.
-
02
Read what it wrote
The code arrives in the panel in full, never truncated. You approve the source, not a summary of it.
-
03
Keep it
A second after it works, the panel asks whether to keep it. Name it, or take the name it suggests.
-
04
Run it by name
Type a slash on that site and it is there. No agent, no waiting, no asking you again.
The name
A tool is named after where it belongs
So you find it by remembering the site, not the tool. Three parts, and only the last one is yours to choose.
/youtube.com:watch:darken-page-except-video-player
The site
Where it was made, and the only place it runs.
The kind of page
The first part of the path. Every watch page, not one video.
What you called it
Yours to name. This is the part you type.
Scope
It offers itself where it belongs, and nowhere else
A tool made on a watch page knows it is for watch pages. It does not follow you around the site, and it never leaves the host.
-
youtube.com/watch?v=anythingoffered -
youtube.com/watch/liveoffered -
youtube.com/resultsnot here -
youtube.comnot here -
music.youtube.com/watchnot here
In practice
The small things a site should have done itself
Every one of these is a few lines the agent writes once, on a page you use often.
collapse-bot-comments
Fold every automated comment on a pull request so the human ones are left.
archive-newsletters
Clear the promotions out of an inbox in one press instead of forty.
copy-table-as-csv
Take the table a dashboard will not export and put it on the clipboard.
What stays yours
Your tool, in your browser, and nowhere else
The code never leaves the browser
It is kept by the extension. The daemon is told a tool exists and what it does, never how it works.
Nothing runs unread
You saw the source before it ran the first time. Keeping it is what makes later runs free of asking.
No client can reach it
It is not a page tool, so nothing an MCP client can call touches it. The side panel is the only way in.
Gone when you say so
Type slash remove-tools for the list, and a cross beside each. Removing one deletes the code with it.
Stop describing the page. Hand it over.
Free and MIT licensed. No signup, no key to paste, and a fresh install connects to nothing until you pair it yourself.
npx browsentic setup