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/majorupdate/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/majorupdate)<a href="https://agentmods.dev/skills/akaghef/m3e/majorupdate"><img src="https://agentmods.dev/badge/skills/akaghef/m3e/majorupdate/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/majorupdate"><img src="https://agentmods.dev/badge/skills/akaghef/m3e/majorupdate.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.00072 | $0.00352 |
| Opus 5.5 | $0.00029 | $0.00141 |
| Sonnet 5.5 | $0.00014 | $0.00070 |
| Haiku 4.5 | $0.00007 | $0.00035 |
Grade A, and why
majorupdate 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.
What it actually says
Major Update Skill
Promote the current dev-beta branch to main (final release) with a date-based version tag.
Version format
Tag name: v + YYMMDD of today's date (e.g. v260402 for 2026-04-02).
Derive the date from the current date at the time of execution.
Steps
Execute the following sequence in order:
- Confirm with the user before proceeding (this modifies
main) - Determine today's version tag:
vYYMMDD git checkout maingit merge dev-beta --no-ff -m "merge: dev-beta → main (beta promotion to final)"git tag <vYYMMDD> maingit push origin maingit push origin <vYYMMDD>git checkout dev-beta— return to the working branch
Notes
- If there are merge conflicts, stop and report them to the user before proceeding
- If the tag already exists (same-day re-launch), ask the user whether to overwrite or use a suffix (e.g.
v260402-2) - Report the commit range pushed and the tag name on completion
- Do not force-push or rewrite history
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 · 34 lines · 72 tokens per session scan A f74fd6c31a00
majorupdate is a skill published in the GitHub repository akaghef/M3E (11 stars, last pushed 5d ago), licensed MIT. It adds 72 tokens to every session and 352 once invoked, about $0.0003 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
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.