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 agentmods add skills/hssh8917/cc-skills/chrome-extensionnpx skills add hssh8917/cc-skills --skill chrome-extensiongit clone --depth 1 https://github.com/hssh8917/cc-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/hssh8917/cc-skills/chrome-extension)<a href="https://agentmods.dev/skills/hssh8917/cc-skills/chrome-extension"><img src="https://agentmods.dev/badge/skills/hssh8917/cc-skills/chrome-extension.svg" alt="Measured on agentmods" 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.00137 | $0.03909 |
| Opus 5 | $0.00068 | $0.01954 |
| Sonnet 5 | $0.00027 | $0.00782 |
| Haiku 4.5 | $0.00014 | $0.00391 |
Grade A, and why
chrome-extension scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
const res = await fetch(msg.url); This is a copy
100% identical to chrome-extension — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 341 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chrome Extension Development (Manifest V3)
This skill covers everything needed to build, debug, and publish Chrome extensions with MV3. It is organized as a routing document: read this file first to understand the architecture and decision points, then load the relevant reference file for implementation details.
Reference files
Read only the reference files relevant to the current task. Each file is self-contained.
| File | When to read |
|---|---|
references/manifest-v3.md |
Setting up or modifying manifest.json, configuring icons, versioning |
references/service-worker.md |
Background logic, lifecycle, state persistence, alarms, events |
references/content-scripts.md |
Injecting code into pages, isolated/main world, dynamic injection, SPA handling, orphaning |
references/messaging-rpc.md |
Communication between any contexts, typed protocols, RPC layer, async handler patterns |
references/ui-surfaces.md |
Popup, options page, side panel, context menus, commands, notifications, omnibox, devtools panel |
references/storage.md |
chrome.storage (local/sync/session), quotas, reactive patterns, framework hooks |
references/network-csp.md |
HTTP requests from content scripts, CSP bypass relay, declarativeNetRequest, offscreen docs, CORS |
references/permissions.md |
Required/optional permissions, host permissions, activeTab, runtime request flow |
references/web-accessible-resources.md |
Exposing extension files to web pages, security implications |
references/typescript-build.md |
TypeScript setup, project structure, build tools comparison, bundling |
references/publishing.md |
Chrome Web Store submission, review process, rejection reasons, updates, privacy policy |
references/execution-contexts.md |
Communication flow diagrams, per-context capabilities/limits, choosing the right messaging method |
references/debugging-mistakes.md |
DevTools for extensions, testing SW termination, common gotchas, error patterns |
What ships with it
13 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.
- references/content-scripts.md 12 KB
- references/debugging-mistakes.md 9.2 KB
- references/execution-contexts.md 22 KB
- references/manifest-v3.md 7.2 KB
- references/messaging-rpc.md 20 KB
- references/network-csp.md 9.9 KB
- references/permissions.md 8.0 KB
- references/publishing.md 6.4 KB
- references/service-worker.md 11 KB
- references/storage.md 9.0 KB
- references/typescript-build.md 8.2 KB
- references/ui-surfaces.md 9.7 KB
- references/web-accessible-resources.md 3.1 KB
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 · 341 lines · 137 tokens per session scan A 23c6823e2f85
chrome-extension is a skill published in the GitHub repository hssh8917/cc-skills (2 stars, last pushed 2d ago), licensed MIT. It adds 137 tokens to every session and 3,909 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to chrome-extension, differing in 6 lines, and is treated as a copy.
Other skills, from other repositories
dingtalk_channel_connect
Use a headed browser to automatically complete DingTalk channel integration for QwenPaw. Applicable when the user mentions DingTalk, developer console, Client ID, Client Secret, bot, Stream mode, binding or configuring a channel. Supports pausing when a login page is detected and resuming after the user logs in.
dingtalk_channel_connect
使用可视浏览器自动完成 QwenPaw 的钉钉频道接入。适用于用户提到钉钉、DingTalk、开发者后台、Client ID、Client Secret、机器人、Stream 模式、绑定或配置 channel 的场景；支持遇到登录页时暂停，等待用户登录后继续。.
browser_cdp
Use this skill when the user explicitly wants to connect to a running Chrome browser, scan local CDP ports, specify a cdpport, or share a single browser across multiple agents/tools. By default browser opens no debugging port; pass an explicit cdpport only when the user wants another local tool to attach.
browser_cdp
当用户明确希望连接到已运行的 Chrome 浏览器、扫描本地 CDP 端口、显式指定 cdpport，或让多个 agent / 工具共享同一个浏览器时，使用本 skill。browser 默认不开放调试端口；仅当用户明确希望其他本地工具附加时才显式传入 cdpport。.
browser_visible
当用户需要控制 browser 的浏览器启动方式时，使用本 skill。browser 默认由 Playwright 直接管理、不开放调试端口（需让其他本地工具附加时显式传 cdpport）；headed 控制是否显示窗口，privatemode 保留用于兼容、不再改变默认行为，browserargs 传入额外的 Chromium 启动参数，executablepath 指定自定义浏览器可执行文件路径。.
browser_visible
Use this skill when the user needs to control the browser launch mode for browser. By default browser is managed by Playwright and opens no debugging port (pass an explicit cdpport to let another local tool attach); headed controls whether the window is visible, and privatemode is kept for backward compatibility and…