What is release-extension?

A release workflow for packaging a Chrome extension, a browser add-on, and publishing it as a GitHub Release. It also updates the extension version and release webpage.

Use it to inspect changes, choose a version, update the manifest, create a ZIP archive, commit and push the version bump, and publish the release.

It keeps version changes, packaged files, source commits, and the published release aligned.

How metedata/Remarc configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to metedata/Remarc. 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/metedata/Remarc/main/.claude/skills/release-extension/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/metedata/Remarc

Made for: Claude Code.

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/skills/metedata/remarc/release-extension/github.svg)](https://agentmods.dev/skills/metedata/remarc/release-extension)

Your own site

<a href="https://agentmods.dev/skills/metedata/remarc/release-extension"><img src="https://agentmods.dev/badge/skills/metedata/remarc/release-extension/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/skills/metedata/remarc/release-extension"><img src="https://agentmods.dev/badge/skills/metedata/remarc/release-extension.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 859 The whole file, excluding the scripts and references it only reads on demand.

Security scan C 2 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.00025	$0.00859
Opus 5.5	$0.00010	$0.00344
Sonnet 5.5	$0.00005	$0.00172
Haiku 4.5	$0.00003	$0.00086

Measured 2mo ago against content hash c8248759ed5e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

release-extension scanned grade C with 2 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 2mo 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf /tmp/remarc-ext/remarc-extension

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -sIL https://github.com/metedata/Remarc/releases/download/extension-vVERSION/Remarc-Extension-VERSION.zip | head -1

.claude/skills/release-extension/SKILL.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.

Release Chrome Extension

Package the Remarc Chrome extension and publish it as a GitHub Release on metedata/Remarc.

Steps

Check current version - Read extension/manifest.json to get the current version
Check what changed - Run git log --oneline on the extension directory since the last version bump to see what's new:
```
git log --oneline -- extension/
```
Prompt for version - Ask the user what version to release (suggest next patch/minor based on changes)
Bump version - Update version in extension/manifest.json

Package - Create a zip with the extension files inside a remarc-extension/ folder:

mkdir -p /tmp/remarc-ext
rm -rf /tmp/remarc-ext/remarc-extension
cp -R extension/ /tmp/remarc-ext/remarc-extension/
cd /tmp/remarc-ext
zip -r Remarc-Extension-VERSION.zip remarc-extension/

Commit and push the manifest bump first - so the release tag points at a commit containing the released source:
```
git add extension/manifest.json
git commit -m "Release extension vVERSION"
git push
```
Create the GitHub Release - on its own extension-v tag, and ALWAYS with --latest=false:
```
gh release create extension-vVERSION /tmp/remarc-ext/Remarc-Extension-VERSION.zip \
  --repo metedata/Remarc \
  --title "Remarc Chrome Extension vVERSION" \
  --latest=false \
  --notes "- what changed"
```
NEVER omit --latest=false. GitHub's releases/latest is repo-global; without the flag this release becomes "latest" and releases/latest/download/Remarc.zip (the app's /download redirect and README link) starts 404ing for every visitor and update check.
Update web page - Update website/public/chrome-extension/index.html:
- Update the download URL to https://github.com/metedata/Remarc/releases/download/extension-vVERSION/Remarc-Extension-VERSION.zip
- Update the version in the download-meta div

Verify:

curl -sIL https://github.com/metedata/Remarc/releases/download/extension-vVERSION/Remarc-Extension-VERSION.zip | head -1
curl -sIL https://github.com/metedata/Remarc/releases/latest/download/Remarc.zip | head -1

Both must return 200: the first proves the extension asset is live, the second proves the app's latest URL was not hijacked.

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.

2mo ago First seen · 77 lines · 25 tokens per session scan C c8248759ed5e

Subscribe to this mod's changes

release-extension is a skill published in the GitHub repository metedata/Remarc (83 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 859 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Browser automation Git and workflow Releases ai-agents developer-tools macos model-context-protocol screen-annotation swift

release-extension next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
release-extensionmetedata/Remarc	Skill	83	1mo ago	MIT	C	25	Claude Code
chrome-releaseschromium/chromium	Skill	25k	yesterday	BSD-3-Clause	A	66	Claude Code, Codex
multi-agent-release-managerchromium/chromium	Skill	25k	yesterday	BSD-3-Clause	A	27	Claude Code, Codex
peekabooopenclaw/Peekaboo	Skill	5.4k	yesterday	MIT	A	37	Claude Code, Codex
git-wrapupcyanheads/obsidian-mcp-server	Skill	702	6d ago	Apache-2.0	A	109	Claude Code
release-and-publishcyanheads/obsidian-mcp-server	Skill	702	6d ago	Apache-2.0	A	155	Claude Code
release-pr-reviewcyanheads/obsidian-mcp-server	Skill	702	6d ago	Apache-2.0	A	136	Claude Code

Remarc: Skill for Claude Code