extension

A command for creating, developing, and building browser extensions with extension.dev, a platform for browser-extension projects.

In plain words
What is it for?
Scaffolding a new extension, starting development with live reloading, and creating production builds for Chrome or Firefox.
Why use it?
It turns common extension tasks into guided commands with the project’s expected development and build steps.

Command

Install

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.

agentmods
npx agentmods add commands/extensiondev/mcp/extension
Clone the repo
git clone --depth 1 https://github.com/extensiondev/mcp
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 874 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00012 $0.00874
Opus 5 $0.00006 $0.00437
Sonnet 5 $0.00002 $0.00175
Haiku 4.5 $0.00001 $0.00087

Measured yesterday against content hash 245208730631, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 yesterday.

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.

2. If not, check the template catalog: `curl -sL https://github.com/extension-js/examples/releases/download/nightly/templates-meta.json | jq '.templates[] | {slug, description, uiFramework, surfaces}'`
claude/commands/extension.md · 77 lines

How it starts

The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are helping build a browser extension with the extension.dev platform. The user said: $ARGUMENTS

Actions

Parse the user's intent from $ARGUMENTS and execute the matching action:

"create " or "new ", Scaffold a new extension

  1. If MCP tool extension_templates is available, use it to find the best template matching the user's description (check for surface type, framework, and keywords)
  2. If not, check the template catalog: curl -sL https://github.com/extension-js/examples/releases/download/nightly/templates-meta.json | jq '.templates[] | {slug, description, uiFramework, surfaces}'
  3. Run npx extension@latest create <name> --template=<best-match>
  4. Report what was created and suggest npm run dev

"dev" or "run", Start development

  1. Run npm run dev (or npx extension dev) in the project root
  2. Tell the user the browser will open with their extension loaded
  3. Mention HMR is active, changes will hot-reload

"build", Build for production

  1. Run npm run build (or npx extension build)
  2. After success, report the output in dist/chrome/
  3. If the user mentions "firefox" or "both", also build with --browser=firefox
  4. If they mention "zip" or "store", add --zip

"add ", Add a feature surface

  1. If MCP tool extension_add_feature is available, use it to get the manifest additions and file list
  2. Otherwise, determine what's needed from the feature type:
    • sidebar: chromium:side_panel + firefox:sidebar_action + sidePanel permission + background handler
    • popup: chromium:action + firefox:browser_action
    • content-script: content_scripts array in manifest
    • newtab: chrome_url_overrides.newtab
    • background: background.service_worker (Chromium) + background.scripts (Firefox)
  3. Create the files and update src/manifest.json

"debug" or "inspect", Debug a running extension

  1. If MCP tool extension_inspect is available, use it with include: ["html", "console", "extension_roots"]
  2. If there's a URL mentioned, pass it as the target
  3. If there are CSS selectors mentioned, pass them as probe
  4. Report: injected HTML, console errors, extension root state

Read the full file on GitHub · 77 lines

Changes

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.

  1. yesterday First seen · 77 lines · 12 tokens per session scan A 245208730631

Subscribe to this mod's changes

extension is a command published in the GitHub repository extensiondev/mcp (1 stars, last pushed 2d ago), licensed Apache-2.0. It adds 12 tokens to every session and 874 once invoked, about $0.0001 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-31.