Borrowing it
Nothing to install: this file belongs to akaghef/M3E. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/akaghef/M3E/main/.claude/skills/launch-final/SKILL.mdgit clone --depth 1 https://github.com/akaghef/M3EWrote 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/akaghef/m3e/launch-final)<a href="https://agentmods.dev/skills/akaghef/m3e/launch-final"><img src="https://agentmods.dev/badge/skills/akaghef/m3e/launch-final/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.
<a href="https://agentmods.dev/skills/akaghef/m3e/launch-final"><img src="https://agentmods.dev/badge/skills/akaghef/m3e/launch-final.svg" alt="Reviewed on agentmods" width="80" 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.00197 | $0.03225 |
| Opus 5.5 | $0.00079 | $0.01290 |
| Sonnet 5.5 | $0.00039 | $0.00645 |
| Haiku 4.5 | $0.00020 | $0.00323 |
Grade A, and why
launch-final 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 5d 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 — 384 lines — stays where its author put it; the contents beside it link to each section on GitHub.
launch-final — Beta to Final プロモーション
beta/ で検証済みのコードを final/ へ同期し、本番品質で固定するフロー。
差分プレビュー → コピー + ビルド → 既存テスト(tsc, vitest)
→ コミット(dev-beta) → push(dev-beta)
→ main マージ(ローカル)
→ vm_test.bat ──────────┐
→ 手動確認(ブラウザ等) ──┤ 並行
↓
→ ✋「両方OK？origin/main に push する？」
→ origin/main push → タグ付与 + push
基本原則
- final/ で新機能を先行開発しない。変更は常に beta/ → final/ の一方向
- 同期は exclude 方式: beta/ を丸ごとコピーし、除外リストに該当するものだけ除く
- ユーザーデータ（SQLite の作業DB）はリポジトリ外。スキーマ変更時のみ migration script を用意する
- final/ の独自ファイル（
FINAL_POLICY.md等）は同期対象外として保護する - リリースゲートは origin/main push 前の1箇所のみ。VM検証 + 手動確認の両方がOKで通過
Step 1: 事前チェック
現在の状態を確認する。
git branch --show-current # dev-beta であること
git status # clean であること
git log --oneline -5 -- final/ # final/ の最終更新を確認
dev-beta 以外のブランチにいる場合は checkout する。 uncommitted changes がある場合はユーザーに確認する。
Step 2: 差分確認
beta/ と final/ の差分を把握する。何が変わるか先にユーザーに見せる。
# ソースの差分サマリー（除外対象を除く）
diff -rq beta/ final/ \
--exclude node_modules --exclude dist \
--exclude .env --exclude Beta_Policy.md --exclude FINAL_POLICY.md \
--exclude prompts --exclude tmp --exclude public \
--exclude e2e_test_server.js --exclude playwright.e2e.config.js \
--exclude backups --exclude audit --exclude conflict-backups \
--exclude .m3e-launched --exclude M3E_dataV1.sqlite \
| head -40
差分がない場合は「final/ は最新です」と報告して終了。
差分がある場合、変更サマリーをユーザーに提示する:
## Final ローンチ差分
変更ファイル: {n}件
主な変更:
- {概要1}
- {概要2}
...
Step 3: 同期（exclude 方式）
beta/ を丸ごと final/ にコピーし、除外リストに該当するものだけスキップする。
除外リスト
| 対象 | 理由 |
|---|---|
node_modules/ |
再インストールする |
dist/ |
再ビルドする |
.env |
開発用シークレット |
Beta_Policy.md |
beta 固有ドキュメント |
prompts/ |
開発用プロンプト |
tmp/ |
一時ファイル |
public/ |
開発用アセット |
e2e_test_server.js |
E2Eテスト専用 |
playwright.e2e.config.js |
同上 |
data/M3E_dataV1.sqlite |
作業DB（final 側は初期化済み） |
data/backups/ |
ランタイム生成物 |
data/audit/ |
同上 |
data/conflict-backups/ |
同上 |
data/.m3e-launched |
初回起動フラグ |
What ships with it
2 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.
- 5d ago First seen · 384 lines · 197 tokens per session scan A 4415f224a6ef
launch-final is a skill published in the GitHub repository akaghef/M3E (11 stars, last pushed 5d ago), licensed MIT. It adds 197 tokens to every session and 3,225 once invoked, about $0.0008 per session on Opus 5.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-10-02.
Other skills, from other repositories
factory-ship
Experimental workflow for publishing and completing configured software delivery work. Use when the user or an enabled factory policy asks to ship.
gitlab-devops
GitLab DevOps operations — issues, merge requests, CI/CD pipelines, repository browsing, labels, milestones, releases, and wiki management. Use when querying GitLab project status, monitoring pipeline executions, browsing repository files, creating issues for network findings, opening merge requests for config…
seed-snapshot-release
An automated workflow for creating and tracking a snapshot release of the pull request on the current branch. A snapshot release is a temporary package build used for testing a branch before a normal release.
push-ci
Push to remote and monitor CI. Validates branch safety, executes git push WITH explicit user approval, then monitors CI run status via gh CLI. Use when: user says 'push', 'push and watch CI', 'ship it', 'push-ci'. Not for: committing (use /smart-commit), creating PRs (use /create-pr), merging (use /merge-prep).
release-engineering
Plan and verify software releases with versioning, changelogs, release branches, feature flags, canaries, migration gates, rollback, deployment checks, and release readiness. Use when preparing a release, shipping a risky PR, coordinating app/backend/database rollout, recovering from a bad deploy, or defining release…
ct-release-orchestrator
Orchestrates the canonical 4-verb release pipeline introduced by SPEC-T9345: cleo release plan, then cleo release open, then PR + GHA tag workflow, then cleo release reconcile. The deprecated cleo release ship monolith was deleted in T10103 — do not invoke it. Use ship-e2e-smoke to validate the full pipeline…