Agent Plugins Marketplace
← All plugins

browser-extension-engineering

v0.2.2

Browser-extension-engineering team — agents (extension-architect, extension-implementation-engineer) for building, shipping, and maintaining cross-browser extensions on Manifest V3: the service-worker background model (and the MV2->MV3 lifecycle trap), content-script isolation + message passing, the permissions/host-permissions model and least-privilege posture, storage, the Chrome Web Store / Edge Add-ons / Firefox AMO review pipelines, and the WebExtensions cross-browser delta. Distinct from frontend-engineering (app-grade React UI) and desktop-app-engineering (Electron/Tauri). skills (build-browser-extension, manifest-permissions-audit, store-submission-readiness), a knowledge bank (a where-should-this-logic-live tree across the four MV3 contexts, MV3 architecture + a permissions-minimization tree, a dated cross-browser note), best-practices. Security verdicts escalate to security-engineering. Requires ravenclaude-core@>=0.7.0.

Claude Code3 Skills

By Matt CorbettLicense: MIT7 GitHub starsUpdated last week

Directory evidence

Runtimes
Claude Code
Parsed components
3 skill or MCP entries
Source updated
Sep 15, 2026
Manifest status
Canonical path parsed

The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →

Install browser-extension-engineering for Claude Code

Installs for the current user
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install browser-extension-engineering@agent-plugin-marketplace

Paste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.

The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.

Get the source manually
git clone https://github.com/mcorbett51090/RavenClaude

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/browser-extension-engineering/.

Plugin files

plugins/browser-extension-engineering/
├── .claude-plugin/plugin.json
├── skills/build-browser-extension/SKILL.md
├── skills/manifest-permissions-audit/SKILL.md
└── skills/store-submission-readiness/SKILL.md

Included Skills3

build-browser-extensionskills/build-browser-extension/SKILL.md

End-to-end workflow to build a Manifest V3 browser extension: decide which context owns each piece of logic (content script vs MV3 service worker vs injected page script vs popup/options), wire messaging between contexts, request the narrowest permissions (activeTab -> optional -> host -> all_urls), and pass Chrome/Edge/Firefox store review. Complements the manifest-permissions-audit and store-submission-readiness skills. The popup/options UI seams to frontend-engineering.

manifest-permissions-auditskills/manifest-permissions-audit/SKILL.md

Audit a browser extension's manifest.json against the least-privilege bar and Manifest V3 conformance: every permission and host match justified, activeTab/optional-permission opportunities, no remotely-hosted code, scoped web_accessible_resources, and the store-review risk each entry carries. Reach for this before a store submission, after a permissions rejection, or when reviewing an inherited extension.

store-submission-readinessskills/store-submission-readiness/SKILL.md

A pre-submission readiness checklist for shipping a browser extension to the Chrome Web Store, Edge Add-ons, and Firefox AMO: required listing metadata, the privacy + permissions justification, single-purpose conformance, data-disclosure forms, and the common rejection reasons to pre-empt. Reach for this before a first submission, after a rejection, or when adding a new store target. Store-policy specifics are volatile — verify against current store docs.

Plugin manifests1

plugins/browser-extension-engineering/.claude-plugin/plugin.json
{
  "name": "browser-extension-engineering",
  "version": "0.2.2",
  "description": "Browser-extension-engineering team — agents (extension-architect, extension-implementation-engineer) for building, shipping, and maintaining cross-browser extensions on Manifest V3: the service-worker background model (and the MV2->MV3 lifecycle trap), content-script isolation + message passing, the permissions/host-permissions model and least-privilege posture, storage, the Chrome Web Store / Edge Add-ons / Firefox AMO review pipelines, and the WebExtensions cross-browser delta. Distinct from frontend-engineering (app-grade React UI) and desktop-app-engineering (Electron/Tauri). skills (build-browser-extension, manifest-permissions-audit, store-submission-readiness), a knowledge bank (a where-should-this-logic-live tree across the four MV3 contexts, MV3 architecture + a permissions-minimization tree, a dated cross-browser note), best-practices. Security verdicts escalate to security-engineering. Requires ravenclaude-core@>=0.7.0.",
  "author": {
    "name": "Matt Corbett"
  },
  "homepage": "https://github.com/mcorbett51090/RavenClaude",
  "license": "MIT",
  "keywords": [
    "browser-extension",
    "manifest-v3",
    "chrome-extension",
    "webextensions",
    "service-worker",
    "content-script",
    "host-permissions",
    "message-passing",
    "chrome-web-store",
    "firefox-amo",
    "edge-add-ons",
    "cross-browser"
  ],
  "requires": {
    "plugins": [
      "ravenclaude-core@>=0.7.0"
    ]
  }
}

For maintainers

If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.

[browser-extension-engineering on Agent Plugins Marketplace](https://pluginsmp.com/plugins/browser-extension-engineering)