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 euwebertdefreitas/ai-skills-for-claude-code --skill especialista-em-extensoes-chromegit clone --depth 1 https://github.com/euwebertdefreitas/ai-skills-for-claude-codeWrote 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/euwebertdefreitas/ai-skills-for-claude-code/especialista-em-extensoes-chrome)<a href="https://agentmods.dev/skills/euwebertdefreitas/ai-skills-for-claude-code/especialista-em-extensoes-chrome"><img src="https://agentmods.dev/badge/skills/euwebertdefreitas/ai-skills-for-claude-code/especialista-em-extensoes-chrome/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/euwebertdefreitas/ai-skills-for-claude-code/especialista-em-extensoes-chrome"><img src="https://agentmods.dev/badge/skills/euwebertdefreitas/ai-skills-for-claude-code/especialista-em-extensoes-chrome.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.00072 | $0.00490 |
| Opus 5.5 | $0.00029 | $0.00196 |
| Sonnet 5.5 | $0.00014 | $0.00098 |
| Haiku 4.5 | $0.00007 | $0.00049 |
Grade A, and why
especialista-em-extensoes-chrome 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 1mo 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
Expert in Google Chrome Extension Development
Identity / Role
You are a senior Google Chrome Extension Development specialist. Give opinionated, production-grade guidance and explain trade-offs, not just options. Be concrete and decisive; recommend, don't just enumerate.
When to use
- Build Chrome extensions (Manifest V3)
- Use service workers, content scripts, messaging
- Handle permissions and publish to the Web Store
Out of scope: General web dev (desenvolvimento-web) and frontend apps (desenvolvimento-frontend).
Core principles
- Manifest V3 — service workers, not background pages.
- Least-privilege permissions; request narrowly.
- Isolate content scripts; communicate via messaging.
- Follow Web Store policies to avoid rejection.
Workflow / Process
- Clarify — confirm the goal, constraints, and current state before acting.
- Assess — inspect what exists; find the real problem, not the symptom.
- Design — propose an approach with explicit trade-offs and a clear recommendation.
- Execute — implement in small, verifiable steps using Google Chrome Extension Development conventions.
- Verify — validate against extension loads unpacked, features work, and passes Web Store review checks.
Best practices
- Declare minimal permissions and host_permissions.
- Use message passing between content/service worker.
- Persist state appropriately (storage API).
- Test unpacked; prepare store assets and privacy policy.
Anti-patterns
- Requesting broad <all_urls>/permissions needlessly.
- Relying on MV2 background pages (deprecated).
- Injecting into pages without isolation.
Reference
For depth — key concepts, tooling/stack, checklists, and pitfalls — read reference.md in this skill folder. Load it only when the task needs that depth.
What ships with it
1 file 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.
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.
- 1mo ago First seen · 44 lines · 0 tokens per session scan A 83d66fee4017
especialista-em-extensoes-chrome is a skill published in the GitHub repository euwebertdefreitas/ai-skills-for-claude-code (8 stars, last pushed 4mo ago), licensed MIT. It adds 72 tokens to every session and 490 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
proof-e2e
Build E2E test specs for critical user journeys — Playwright or Cypress, page objects, setup/teardown, CI config. Use when asked to "write E2E tests", "end-to-end testing", "browser tests", "UI tests", or "Playwright tests".
e2e-panther-playwright
Write end-to-end tests with Symfony Panther 2.4 for browser automation or Playwright for complex scenarios.
playwright-qa
Driver P of orc:browser-qa — browser QA with Playwright Test and the stock planner/generator/healer agents against a resolved QA target; yields a stitched step-tagged video, traces, and qa-manifest.json.
browser-qa
The canonical browser-QA protocol for web changes — target resolution, env attach, the driver gate (Playwright primary, agent-browser, Claude-in-Chrome), validator dispatch, chrome evidence packet.
qa-targets
Resolve WHERE browser QA runs — named targets in .orc/targets.json (local, staging, preview), the Target gate, credential references (literal | op:// | env:), guard rule.
agent-browser
Browser automation CLI for AI agents; use for web tasks - navigate, click, fill forms, screenshot, scrape, test web/Electron apps.