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.
git clone --depth 1 https://github.com/fullselfbrowsing/FSBWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/plugins/fullselfbrowsing/fsb/grok-bot)<a href="https://agentmods.dev/plugins/fullselfbrowsing/fsb/grok-bot"><img src="https://agentmods.dev/badge/plugins/fullselfbrowsing/fsb/grok-bot/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/plugins/fullselfbrowsing/fsb/grok-bot"><img src="https://agentmods.dev/badge/plugins/fullselfbrowsing/fsb/grok-bot.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
full-self-browsing 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 8d 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.
What it actually says
{
"name": "full-self-browsing",
"version": "0.1.0",
"description": "Connect Grok Bot to Full Self Browsing on its own computer for supervised browser actions, DOM reads and application capabilities.",
"author": {
"name": "Full Self Browsing"
},
"homepage": "https://www.full-selfbrowsing.com",
"license": "MIT",
"mcpServers": "mcp.json",
"keywords": [
"full self browsing",
"fsb mcp",
"fsb-mcp-server",
"fsb extension"
],
"logo": "assets/logo.png",
"repository": "https://github.com/fullselfbrowsing/FSB"
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 26 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 8d ago First seen · 20 lines scan A 7e4f478a7b3b
full-self-browsing is a plugin published in the GitHub repository fullselfbrowsing/FSB (193 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-10-09.
Other plugins, from other repositories
extension-mcp
MCP tools for browser extension development: scaffold from 50+ templates, run the dev server with HMR, inspect the live DOM and logs, and build store-ready bundles for Chrome, Edge, and Firefox. Ships /extension, /extension-add, /extension-debug, and /extension-publish commands.
browser-harness
Direct browser control via CDP. Drives the user's real Chrome (or a Browser Use cloud browser) with coordinate clicks, screenshots, and Python helpers — no selector hunting. Requires the one-time browser-harness CLI install (see the skill's references/install.md).
unbrowse
Websites as APIs: read pages, run site tasks via learned APIs, and a cloud browser with saved logins.
browser-relay
Let agents use the Chrome you already have open and logged in through a Skill + CLI, locally or across machines.
firecrawl
Web scraping, search, crawling, and file parsing through the firecrawl-cli binary with a write-to-disk-then-Read pattern that keeps large results out of context: a user-facing wrapper skill, a lazy-install setup skill, and a separate gated maintainer update skill tracking the upstream CLI and skill source.
chrome-bridge
Borrow a tab from your own logged-in Chrome and hand it back: navigate, read, fill, audit, diff and record in the browser you already use; logins, 2FA and CAPTCHAs stay with you (handoff). ChromeOS included; the debugger only on request (trusted input, traces, video). Ships the chrome-bridge skill (recipes) and the…