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 quangpl/browser-extension-skills --skill extension-devgit clone --depth 1 https://github.com/quangpl/browser-extension-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/quangpl/browser-extension-skills/extension-dev)<a href="https://agentmods.dev/skills/quangpl/browser-extension-skills/extension-dev"><img src="https://agentmods.dev/badge/skills/quangpl/browser-extension-skills/extension-dev.svg" alt="Measured on agentmods" 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.00030 | $0.01435 |
| Opus 5 | $0.00015 | $0.00718 |
| Sonnet 5 | $0.00006 | $0.00287 |
| Haiku 4.5 | $0.00003 | $0.00144 |
Grade A, and why
extension-dev 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Extension Dev
Detect the stack, find docs, implement the feature, debug. Do NOT just explain — execute the workflow.
Workflow (Execute This)
Step 1: Detect framework and UI stack
Run detection (see references/framework-detection.md):
ls wxt.config.ts plasmo.config.ts vite.config.ts manifest.json 2>/dev/null
cat package.json | grep -E '"wxt|plasmo|crxjs|react|vue|svelte"'
| File found | Framework |
|---|---|
wxt.config.ts |
WXT |
package.json has plasmo |
Plasmo |
vite.config has @crxjs |
CRXJS |
manifest.json in root, none above |
Vanilla |
Step 2: Fetch framework docs and style guides
Use docs-seeker skill or web search to find proper docs for the detected stack.
Extension framework docs:
- WXT: https://wxt.dev/ | Plasmo: https://docs.plasmo.com/ | CRXJS: Vite plugin docs
- Chrome APIs: https://developer.chrome.com/docs/extensions/reference/api
- Permissions: https://developer.chrome.com/docs/extensions/reference/permissions-list
UI framework docs (fetch based on detected framework):
| Framework | Docs | Style Guide |
|---|---|---|
| React | https://react.dev | https://react.dev/learn |
| Next.js | https://nextjs.org/docs | https://nextjs.org/docs/app |
| Vue | https://vuejs.org/guide | https://vuejs.org/style-guide |
| Svelte | https://svelte.dev/docs | https://svelte.dev/docs |
| SolidJS | https://solidjs.com/docs | https://solidjs.com/guides |
| Angular | https://angular.dev/guide | https://angular.dev/style-guide |
Code style guides (always follow):
- TypeScript: https://google.github.io/styleguide/tsguide.html
- JavaScript: https://google.github.io/styleguide/jsguide.html
Step 3: Implement the feature
Follow framework conventions:
- WXT: add entrypoints in
entrypoints/, configurewxt.config.ts - Plasmo: add pages/tabs/contents, use CSUI for content UI
- CRXJS: standard Vite + manifest-based setup
- Vanilla: edit
manifest.json, add JS files directly
What ships with it
5 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.
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.
- 8d ago First seen · 149 lines · 30 tokens per session scan A 2cf8b6b548a4
extension-dev is a skill published in the GitHub repository quangpl/browser-extension-skills (48 stars, last pushed 2mo ago), licensed MIT. It adds 30 tokens to every session and 1,435 once invoked, about $0.0002 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.
Other skills, from other repositories
chrome-extension
Use when building or shipping a Manifest V3 browser extension and hitting its quirks — service worker dying and losing state, permission warnings, a Chrome Web Store rejection, content-script/worker/popup messaging, or an MV2-to-V3 migration. NOT a generic web app (that is nextjs), NOT a desktop shell (that is…
browser-extension-patterns
Build browser extensions with Manifest V3 for Chrome, Firefox, and cross-browser compatibility. Covers content scripts, background workers, popup UI, storage APIs, and extension messaging. Triggers on browser extension development, Manifest V3, or Chrome extension requests.
design-taste-frontend
Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.
image-to-code
Elite website image-to-code skill for Codex. For visually important web tasks, it must first generate the design image(s) itself, deeply analyze them, then implement the website to match them as closely as possible. In Codex, it must prefer large, readable, section-specific images instead of tiny compressed boards…
design-taste-frontend-v1
The original v1 taste-skill, preserved for projects depending on its exact behavior. The current default is design-taste-frontend (v2 experimental), which is a substantial rewrite. Use this v1 install name only if you need exact backward compatibility.
redesign-existing-projects
Upgrades existing websites and apps to premium quality. Audits current design, identifies generic AI patterns, and applies high-end design standards without breaking functionality. Works with any CSS framework or vanilla CSS.