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.
/plugin marketplace add whit3rabbit/camoufox-mcpnpx agentmods add plugins/whit3rabbit/camoufox-mcp/camoufoxgit clone --depth 1 https://github.com/whit3rabbit/camoufox-mcpWrote 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/whit3rabbit/camoufox-mcp/camoufox)<a href="https://agentmods.dev/plugins/whit3rabbit/camoufox-mcp/camoufox"><img src="https://agentmods.dev/badge/plugins/whit3rabbit/camoufox-mcp/camoufox.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
camoufox 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 5d 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": "camoufox",
"displayName": "Camoufox",
"version": "2.5.0",
"description": "Bundle Camoufox MCP browser automation tools and usage guidance.",
"author": {
"name": "followthewhit3rabbit",
"url": "https://github.com/whit3rabbit"
},
"homepage": "https://github.com/whit3rabbit/camoufox-mcp#readme",
"repository": "https://github.com/whit3rabbit/camoufox-mcp",
"license": "MIT",
"keywords": [
"mcp",
"camoufox",
"browser",
"automation",
"privacy",
"anti-detection"
],
"skills": "./skills/",
"mcpServers": "./.mcp.json"
}
What it installs
The manifest is a name and a version. 1 skill, 1 MCP server travel with it, and installing the plugin installs all of them — 93 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.
- 5d ago First seen · 24 lines scan A 2e0f1ce23e2a
camoufox is a plugin published in the GitHub repository whit3rabbit/camoufox-mcp (46 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-08-30.
Other plugins, from other repositories
kernel-sdks
TypeScript and Python SDK skills for building browser automation with Kernel's Typescript and Python SDKs.
sniff
Autonomous QA scanner via sniff-qa: walks your running app in a real browser and reports real bugs (broken pages/links, console/network errors, broken forms, state-loss, empty/placeholder data, bad loading/error states, responsive + a11y) with reproduction proof, severity, confidence, and a fix. No API key.
realbrowser
Target-first local Chrome/Chromium browser control with signed-in profiles, labeled tabs, and guarded actions.
rad-chrome-extension
MV3 Chrome extension development standards (WXT, React, TypeScript) with two pure-stdlib Python validators that catch what LLM eyeballing misses. Skills cover architecture, MV3 security (CSP, remote code ban, content script isolation), permission minimization and CWS compliance, typed messaging, storage selection…
chrome-multi-instance-warn
An agent driving a browser tends to start a new one rather than use the one already open, and to size its work off the core count. This warns once per session when a tool payload is about to do either. Never blocks.
headless
Headless browser automation for site comparison, E2E testing, and anti-bot-aware web research.