They help develop and build Chrome and Firefox extensions, add file-based Vue pages, manage shared state with Pinia, connect extension contexts, lint code, and run type checks.

They show agents where browser-extension code belongs and which commands check or build it. This reduces mistakes when working across popups, background code, content scripts, and other extension areas.

How mubaidr/vite-vue3-browser-extension-v3 configures GitHub Copilot

Q: What is vite-vue3-browser-extension-v3 copilot-instructions.md?

Coding-agent instructions for a Vite and Vue 3 browser-extension template using Manifest V3, the browser-extension standard for modern Chrome and Firefox extensions. They describe its contexts, project structure, workflows, and integrations.

Reuse

Borrowing it

Nothing to install: this file belongs to mubaidr/vite-vue3-browser-extension-v3. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/mubaidr/vite-vue3-browser-extension-v3/master/.github/copilot-instructions.md

Clone the repo

git clone --depth 1 https://github.com/mubaidr/vite-vue3-browser-extension-v3

Made for: GitHub Copilot.

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

README.md

[![agentmods](https://agentmods.dev/badge/instructions/mubaidr/vite-vue3-browser-extension-v3/copilot-instructions/github.svg)](https://agentmods.dev/instructions/mubaidr/vite-vue3-browser-extension-v3/copilot-instructions)

Your own site

<a href="https://agentmods.dev/instructions/mubaidr/vite-vue3-browser-extension-v3/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/mubaidr/vite-vue3-browser-extension-v3/copilot-instructions/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/mubaidr/vite-vue3-browser-extension-v3/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/mubaidr/vite-vue3-browser-extension-v3/copilot-instructions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 618 This file is loaded in full into every session.

When invoked 618 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00618	$0.00618
Opus 5	$0.00309	$0.00309
Sonnet 5	$0.00124	$0.00124
Haiku 4.5	$0.00062	$0.00062

Measured 11d ago against content hash c39c928165eb, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

vite-vue3-browser-extension-v3 copilot-instructions.md 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 11d 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.

.github/copilot-instructions.md · 54 lines

How it starts

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

Copilot AI Agent Instructions

Project Overview

This is a modern, multi-context browser extension template using Vite, Vue 3, and Manifest V3.
Major contexts: background, popup, options, content script, devtools, side panel, offscreen (see src/ subfolders).
UI is modular, file-based, and auto-routed from src/ui/*/pages.
State is managed with Pinia; cross-context communication uses webext-bridge and webextension-polyfill.
UI components: Nuxt/UI v3, shadcn-vue, styled with Tailwind CSS 4.

Key Workflows

Development: npm run dev (runs Chrome and Firefox dev builds concurrently)
Build: npm run build (builds for both Chrome and Firefox)
Lint: npm run lint (ESLint + Prettier)
Typecheck: npm run typecheck (Vue TSC)
Load extension: Use dist/chrome or dist/firefox in browser

Architecture & Patterns

File-based Routing: Add Vue files to src/ui/<context>/pages/ for auto-registration as routes.
Composables: Shared logic in src/composables/ (e.g., theme, i18n, browser storage)
Pinia Stores: State in src/stores/, auto-imported where needed
TypeScript: Strict, enforced everywhere
Auto-imports: Functions, stores, and components are auto-imported (see Vite config)
Error Handling: Use console.info for logging in background/content scripts
Cross-context Communication: Use webext-bridge for messaging between extension contexts

Integration Points

Browser APIs: Use webextension-polyfill for compatibility
UI Components: Use Nuxt/UI and shadcn-vue; add new shadcn-vue components via CLI
i18n: Locales in src/locales/, managed via Vue I18n

Project-specific Conventions

Place new UI pages in src/ui/<context>/pages/
Use composables for shared logic, not mixins
Keep components small and focused
Use strict TypeScript and auto-imports
Prefer file-based routing and modular structure

Examples

See src/background/index.ts for install/update logic
See src/content-script/index.ts for DOM injection
See src/ui/action-popup/app.vue for UI entrypoint pattern
See src/utils/router/index.ts for router setup

Read the full file on GitHub · 54 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.

11d ago First seen · 54 lines · 618 tokens per session scan A c39c928165eb

Subscribe to this mod's changes

vite-vue3-browser-extension-v3 copilot-instructions.md is an instructions file published in the GitHub repository mubaidr/vite-vue3-browser-extension-v3 (790 stars, last pushed 2mo ago), licensed MIT. It adds 618 tokens to every session, about $0.0031 per session on Opus 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-08-30.

Browser automation Frontend Vue and Svelte chrome extension hacktoberfest vite vue3 webextension

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

vite-vue3-browser-extension-v3: Instructions file for GitHub Copilot