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 QuickerHub/quicker-rpc --skill quicker-chromecontrolgit clone --depth 1 https://github.com/QuickerHub/quicker-rpcWrote 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/quickerhub/quicker-rpc/quicker-chromecontrol)<a href="https://agentmods.dev/skills/quickerhub/quicker-rpc/quicker-chromecontrol"><img src="https://agentmods.dev/badge/skills/quickerhub/quicker-rpc/quicker-chromecontrol/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/quickerhub/quicker-rpc/quicker-chromecontrol"><img src="https://agentmods.dev/badge/skills/quickerhub/quicker-rpc/quicker-chromecontrol.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.00038 | $0.00582 |
| Opus 5 | $0.00019 | $0.00291 |
| Sonnet 5 | $0.00008 | $0.00116 |
| Haiku 4.5 | $0.00004 | $0.00058 |
Grade A, and why
quicker-chromecontrol 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 12d 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
quicker-chromecontrol
Route for browser automation against the user's logged-in browser.
See also: docs/browser-automation.md — unified boundary table (Playwright / embedded / extension).
Agent vs action browser
QuickerAgent browser |
user_browser / qkrpc_chrome_control |
sys:chromecontrol steps | |
|---|---|---|---|
| Who runs | Agent Playwright session | Agent via RPC → Quicker extension | User's action at runtime |
| Login state | None (clean profile) | User's cookies / login | User's cookies / login |
| Needs extension | No | Yes (Quicker Connector) | Yes |
| Use for | Agent reads arbitrary URL while designing | Agent operates user's open browser in chat | Production automation in saved actions |
Live control (agent in chat)
user_browser({ action: "tabs" })or MCPqkrpc_chrome_tabs— list connected tabsuser_browser({ action: "run", operation: "OpenUrl", parameters: { url, windowId: "New", waitComplete: true } })- Reuse
sessionId;tabIdfrom OpenUrl is auto-carried when omitted on next run - CLI:
qkrpc chrome run --operation RunScript --params '{"script":"document.title"}' --json
Parameter schema: qkrpc_step_runner_get with key=sys:chromecontrol and controlField = operation.
Authoring actions (on disk)
qkrpc_step_runner_search→sys:chromecontrolqkrpc_step_runner_getwithcontrolField= operationdocs({ action: "get", topic: "chromecontrol-authoring" })- Patch:
reference: "examples/chromecontrol"
Hard rules
- Reuse tabId across steps (
tabId.varin actions; literaltabIdor session in RPC) - RunScript on MV3: user must enable extension Allow user scripts
- Prefer BackgroundCommand over legacy BackgroundScript on MV3
- Do not guess
inputParamskeys — always step_runner_get first
Related
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.
- 12d ago First seen · 47 lines · 38 tokens per session scan A 753571325a23
quicker-chromecontrol is a skill published in the GitHub repository QuickerHub/quicker-rpc (13 stars, last pushed 29d ago), licensed MIT. It adds 38 tokens to every session and 582 once invoked, about $0.0002 per session on Opus 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-08-30.
Other skills, from other repositories
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".
tauri-mcp-cli
Use the Tauri MCP CLI to start and recover driver sessions, automate Tauri webviews, capture UI state, debug IPC, and work with mobile or remote devices. Use whenever an agent needs to operate a Tauri v2 app from terminal commands.
browser-automation
A browser-automation workflow that detects the terminal environment and chooses a browser control tool. It supports opening pages, taking snapshots, clicking, filling fields, and other checks.
playwright-cli
Skill "playwright-cli" from Insajin/autopus-adk, covering browser automation with playwright-cli, quick start, commands, core and navigation.
goofish-overview
An overview and entry point for goofish-cli, a tool package for helping an AI agent operate Xianyu, a Chinese second-hand marketplace. It covers account checks, listing items, buyer messages, risk checks, and shop diagnosis, and directs specific jobs to dedicated workflows.
scout-web-access
Strato web-access cross-provider per gli Scout (F-2). 5 componenti coordinati — anti-bot robust scrape, LinkedIn session + search, email IMAP poll, multi-Scout workspace claim, freshness focus. Usato come stack base per ogni sweep: lo Scout sceglie il livello di accesso più leggero che funziona, e sale solo quando…