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.
npx skills add ainative-build/skills --skill aif-chrome-profilegit clone --depth 1 https://github.com/ainative-build/skillsWrote 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/skills/ainative-build/skills/aif-chrome-profile)<a href="https://agentmods.dev/skills/ainative-build/skills/aif-chrome-profile"><img src="https://agentmods.dev/badge/skills/ainative-build/skills/aif-chrome-profile/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/skills/ainative-build/skills/aif-chrome-profile"><img src="https://agentmods.dev/badge/skills/ainative-build/skills/aif-chrome-profile.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00032 | $0.01948 |
| Opus 5.5 | $0.00013 | $0.00779 |
| Sonnet 5.5 | $0.00006 | $0.00390 |
| Haiku 4.5 | $0.00003 | $0.00195 |
Grade A, and why
aif-chrome-profile 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.
How it starts
The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chrome Profile
Profile-aware browser automation path when the agent needs the user's real Chrome state: the right Google account, cookies, workspace, tenant, or logged-in product session.
This is not the default for ordinary browser testing. Use aif-agent-browser when a fresh or tool-managed browser is enough. Use project-native Playwright or aif-web-testing for repeatable CI tests. Use this skill when the user's actual Chrome profile state matters.
What This Skill Provides
chrome-profile <key> <url>opens a URL in a configured Chrome profile.chrome-profile open --json <key> <url>emits machine-readable binding data for agents.- Profile keys resolve by Google account email or display-name substring, not brittle
Profile 17directory names. chrome-profile doctortells the agent and user whether the opened tab will be readable through a browser bridge.- The opened URL gets
#cdp-profile=<key>&cdp-open=<token>so the agent can bind to the exact tab from a flat MCP tab list. - Setup playbooks cover both required layers: the browser bridge and Chrome profile mapping.
Agent Contract
When this skill is invoked, the agent must lead the user through setup if anything is missing. Do not just say "configure MCP." Run the checks, explain the failing layer, and give the next concrete command or browser action.
Do not treat chrome-profile doctor as the only source of truth. It is a static setup heuristic. Before telling the user that the browser bridge is unavailable, make one live probe through Chrome DevTools MCP if those tools are exposed by the current agent runtime.
Required readiness:
- Profile mapping exists:
chrome-profile listresolves the requested key. - Browser read path exists: a live Chrome DevTools MCP probe can list or read Chrome pages.
- Runtime tab selection works: after opening, MCP page listing contains the exact
cdp-open=<token>from the CLI output or JSON payload.
If the profile mapping fails, pause and guide chrome-profile setup. If the bridge check fails, run the live probe below before asking the user to change MCP setup, relaunch Chrome, or close active tabs.
What ships with it
12 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- LICENSE 1.1 KB
- profiles.example.json 181 B
- references/architecture.md 6.2 KB
- references/mcp-config-recipes.md 9.1 KB
- references/setup-and-bridge.md 3.2 KB
- references/troubleshooting.md 5.2 KB
- scripts/chrome_profile_cli.py 32 KB runs code
- scripts/install.cmd 1.4 KB runs code
- scripts/install.sh 1.1 KB runs code
- scripts/test_chrome_profile.py 18 KB runs code
- scripts/uninstall.cmd 1.6 KB runs code
- scripts/uninstall.sh 1.6 KB runs code
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 · 133 lines · 32 tokens per session scan A f1f04b41a0f2
aif-chrome-profile is a skill published in the GitHub repository ainative-build/skills (10 stars, last pushed 6d ago), licensed MIT. It adds 32 tokens to every session and 1,948 once invoked, about $0.0001 per session on Opus 5.5. 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-23.
Other skills, from other repositories
surf
Drive the user's logged-in Chrome from the shell. Use for browser automation (open, read, click, fill, upload, screenshot), reading a site's feed or API, or asking ChatGPT, Gemini, Perplexity or Grok through the browser.
agentcookie-install
Install agentcookie on a Mac source and a Linux or Mac sink so Chrome cookies sync continuously over Tailscale. Use when the user says "install agentcookie", "set up cookie sync", "share my Chrome sessions with my agent box", or "make my agent log in as me".
webview-devtools
Use webview-devtools-mcp to inspect and automate an already-instrumented WebView/page: choose this skill when the user’s target environment is configured so the page injects wdmcp’s target.js (or the user is explicitly asking to work with such a configured WebView). If the page is not yet injecting target.js, do not…
chrome-devtools-cli
Use this skill to write shell scripts or run shell commands to automate tasks in the browser or otherwise use Chrome DevTools via CLI.
cookie-debugging
Uses Chrome DevTools MCP for inspecting, debugging, and testing cookies, session state, authentication issues, and cookie consent compliance. Use when diagnosing 401/403 errors, authentication redirects, session expiration, Cookie/Set-Cookie header issues, cookie banner consent conformance, or third-party…
a11y-debugging
Uses Chrome DevTools MCP for accessibility (a11y) debugging and auditing based on web.dev guidelines. Use when testing semantic HTML, ARIA labels, focus states, keyboard navigation, tap targets, and color contrast.