extension-publish

extension-publish is a skill for Claude Code, Codex from quangpl/browser-extension-skills. It costs 31 tokens per session (913 once invoked), scanned A, original, MIT.

A submission guide for publishing Chrome extensions in the Chrome Web Store, from preparing files through review and release.

In plain words
What is it for?
Use it to package an extension, check its Manifest V3 details and assets, prepare the listing, submit it, and manage publication.
Why use it?
It helps developers meet store requirements and avoid common rejection causes involving permissions, privacy information, manifests, and listing content.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to package an extension, check its Manifest V3 details and assets, prepare the listing, submit it, and manage publication.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/quangpl/browser-extension-skills/extension-publish
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.

Any agent
npx skills add quangpl/browser-extension-skills --skill extension-publish
Clone the repo
git clone --depth 1 https://github.com/quangpl/browser-extension-skills

Made for: Claude Code, Codex.

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.

agentmods badge for extension-publish

README.md
[![agentmods](https://agentmods.dev/badge/skills/quangpl/browser-extension-skills/extension-publish/github.svg)](https://agentmods.dev/skills/quangpl/browser-extension-skills/extension-publish)
Your own site
<a href="https://agentmods.dev/skills/quangpl/browser-extension-skills/extension-publish"><img src="https://agentmods.dev/badge/skills/quangpl/browser-extension-skills/extension-publish/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.

agentmods 80×15 button for extension-publish

Your own site · 80×15
<a href="https://agentmods.dev/skills/quangpl/browser-extension-skills/extension-publish"><img src="https://agentmods.dev/badge/skills/quangpl/browser-extension-skills/extension-publish.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 913 The whole file, excluding the scripts and references it only reads on demand.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00031 $0.00913
Opus 5 $0.00015 $0.00456
Sonnet 5 $0.00006 $0.00183
Haiku 4.5 $0.00003 $0.00091

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

Security

Grade A, and why

extension-publish 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.

skills/extension-publish/SKILL.md · 124 lines

How it starts

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

extension-publishing

Workflow

prepare → package → submit → review → publish
  1. Prepare: assets, privacy policy, permission justifications, manifest
  2. Package: zip source (exclude dev files), validate manifest
  3. Submit: Chrome Web Store Developer Dashboard
  4. Review: 1–3 days typical; up to 7 days for new publishers
  5. Publish: auto or manual rollout

Pre-Submission Checklist (Quick)

  • Manifest v3 only (MV2 deprecated)
  • name, version, description set in manifest
  • Icons: 16×16, 48×48, 128×128 PNG
  • Screenshots: min 1, 1280×800 or 640×400
  • Single purpose clearly defined
  • Only permissions actually used
  • Privacy policy URL (required if collecting data)
  • Permission justification field filled for sensitive perms
  • No remote code execution (eval, remote scripts)
  • All features functional in review build

Full checklist: references/submission-checklist.md


Top 10 Rejection Reasons

  1. Single purpose violation — does too many unrelated things
  2. Excessive/unnecessary permissions
  3. Missing privacy policy (required when user data collected)
  4. Missing permission justification in submission form
  5. Description doesn't match functionality
  6. Keyword spam in title/description
  7. Remote code execution (eval, external scripts)
  8. Improper user data handling or disclosure
  9. Extension non-functional or crashes
  10. Broken features / inaccessible links

Full details + fixes: references/common-rejections.md


Listing Optimization Essentials

  • Title: <Action verb> + <Benefit>, max 45 chars, no keyword stuffing
  • Description first 150 chars: shown in search — make them count
  • Structure: problem → solution → key benefits → CTA
  • Screenshots: annotate features, show real UI, 1280×800
  • Category: choose most specific fit

Full guide: references/store-listing-optimization.md

Read the full file on GitHub · 124 lines

Files

What ships with it

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

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. 11d ago First seen · 124 lines · 31 tokens per session scan A 8dc1eb2956c5

Subscribe to this mod's changes

extension-publish is a skill published in the GitHub repository quangpl/browser-extension-skills (49 stars, last pushed 3mo ago), licensed MIT. It adds 31 tokens to every session and 913 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.

Related

Other skills, from other repositories

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.

Leonxlnx/taste-skill · 61 tokens

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…

Leonxlnx/taste-skill · 116 tokens

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.

Leonxlnx/taste-skill · 61 tokens

brandkit

Premium brand-kit image generation skill for creating high-end brand-guidelines boards, logo systems, identity decks, and visual-world presentations. Trained for minimalist, cinematic, editorial, dark-tech, luxury, cultural, security, gaming, developer-tool, and consumer-app brand systems. Optimized for intentional…

Leonxlnx/taste-skill · 89 tokens

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.

Leonxlnx/taste-skill · 45 tokens

gpt-taste

Elite UX/UI & Advanced GSAP Motion Engineer. Enforces Python-driven true randomization for layout variance, strict AIDA page structure, wide editorial typography (bans 6-line wraps), gapless bento grids, strict GSAP ScrollTriggers (pinning, stacking, scrubbing), inline micro-images, and massive section spacing.

Leonxlnx/taste-skill · 72 tokens