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 samber/cc-skills --skill chrome-extensiongit clone --depth 1 https://github.com/samber/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/samber/cc-skills/chrome-extension)<a href="https://agentmods.dev/skills/samber/cc-skills/chrome-extension"><img src="https://agentmods.dev/badge/skills/samber/cc-skills/chrome-extension/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/samber/cc-skills/chrome-extension"><img src="https://agentmods.dev/badge/skills/samber/cc-skills/chrome-extension.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk warn
- NVIDIA SkillSpector pass
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.00143 | $0.03916 |
| Opus 5 | $0.00072 | $0.01958 |
| Sonnet 5 | $0.00029 | $0.00783 |
| Haiku 4.5 | $0.00014 | $0.00392 |
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 4d 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); Copies of this mod
1 near-identical copy found in the catalogue:
- chrome-extension — 100% identical, 6 lines differ
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.
- 4d ago Changed · +6 tokens per session 1465c8c9fc7a
- 10d ago First seen · 341 lines · 137 tokens per session scan A 9c4e156b5eba
chrome-extension is a skill published in the GitHub repository samber/cc-skills (207 stars, last pushed 2d ago), licensed MIT. It adds 143 tokens to every session and 3,916 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
golang-testing
Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI…
golang-benchmark
Golang benchmarking, profiling, and performance measurement. Use when writing, running, or comparing Go benchmarks, profiling hot paths with pprof, interpreting CPU/memory/trace profiles, analyzing results with benchstat, setting up CI benchmark regression detection, or investigating production performance with…
golang-continuous-integration
GitHub Actions CI/CD pipeline configuration for Golang projects — workflow files for test, lint, SAST, coverage and vulnerability-scan jobs, Dependabot and Renovate config files, GoReleaser release pipelines, Docker build/push, repository security settings, and AI-driven PR review. Use when setting up or improving Go…
golang-documentation
Comprehensive documentation guide for Golang projects, covering godoc comments, README, CONTRIBUTING, CHANGELOG, Go Playground, Example tests, API docs, and llms.txt. Use when writing or reviewing doc comments, documentation, adding code examples, setting up doc sites, or discussing documentation best practices.…
golang-observability
Golang everyday observability — the always-on signals in production. Covers structured logging with slog, Prometheus metrics, OpenTelemetry distributed tracing, continuous profiling with pprof/Pyroscope, server-side RUM event tracking, alerting, and Grafana dashboards. Apply when instrumenting Go services for…
golang-security
Security best practices and vulnerability prevention for Golang — injection (SQL, command, XSS), cryptography, path traversal, SSRF and HTTP security headers, cookies, secrets management, memory safety, PII in logs, STRIDE/DREAD threat modeling, plus gosec SAST, race detection, and fuzz testing. Apply when writing…