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 stefanrows/claude-code-plugins --skill merge-to-maingit clone --depth 1 https://github.com/stefanrows/claude-code-pluginsWrote 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/stefanrows/claude-code-plugins/merge-to-main)<a href="https://agentmods.dev/skills/stefanrows/claude-code-plugins/merge-to-main"><img src="https://agentmods.dev/badge/skills/stefanrows/claude-code-plugins/merge-to-main/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/stefanrows/claude-code-plugins/merge-to-main"><img src="https://agentmods.dev/badge/skills/stefanrows/claude-code-plugins/merge-to-main.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.00047 | $0.02172 |
| Opus 5.5 | $0.00019 | $0.00869 |
| Sonnet 5.5 | $0.00009 | $0.00434 |
| Haiku 4.5 | $0.00005 | $0.00217 |
Grade A, and why
merge-to-main 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 1mo 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Merge to Main Workflow
A fast, safe workflow for landing changes on main. Operating principles: scope once (detect tooling and the change set in a single pass, then reuse it), fail fast (cheap checks first), parallelize (independent checks run concurrently), skip what can't be affected (don't run checks the change set can't break), and one confirmation gate (batch everything the user must approve into a single question).
Setup
- Git auth: Use GitHub CLI (
gh auth setup-git) when available — avoid manual PAT or SSH configuration.
Phase 1 — Scope (one pass, drives everything after)
- Branch from fresh remote main without touching the local
maincheckout:git fetch origin && git switch -c <type>/<slug> origin/main. Use a conventional prefix (feat/,fix/,docs/,chore/,refactor/,test/). Always a fresh branch — never reuse one. - Detect tooling once. In one pass, read
package.json,pyproject.toml,Makefile,Dockerfile,docker-compose.yml,.github/workflows/, and any docs app (apps/docs,website/, Docusaurus, VitePress, OpenAPI spec, Storybook). Also checkProjectSettings/ProjectVersion.txt— its presence means this is a Unity project; note the exactm_EditorVersionit contains (reuse it verbatim in Phase 3, never guess or use "latest installed"), and also notePackages/manifest.json, any*.asmdef,.gitattributesLFS rules, and Unity CI config (GameCI or Unity Build Automation in.github/workflows/). IfProjectVersion.txtexists, readreferences/unity.mdbefore Phase 3. Note the exact lint/test/build/docs-build commands. Do not re-derive these later. - Compute the change set once:
git diff --name-only origin/main...HEAD(plus planned edits). From it, decide up front which checks apply:- Source code changed → lint + tests + build (+ container build if a Dockerfile exists and code/deps changed).
- Behavior that docs describe changed (APIs, CLI, config/env, UI flows, permissions, error codes) → matching doc pages must be updated in this branch.
- Docs-only change → skip tests/build/container; run only the docs build and link checks if the project has them.
- Lockfile/dependency-only change → tests + build + container; lint of unchanged source adds nothing.
- Unity —
Assets/**/*.cs,*.asmdef,Packages/manifest.jsonchanged → asset integrity + compile + EditMode tests. - Unity —
*.unity,*.prefab,*.asset,*.mat,*.controller(YAML) changed → asset integrity only, no compile needed. - Unity —
ProjectSettings/**changed → asset integrity + compile (build settings can break the player build). - Unity — art/audio/video binaries changed → asset integrity (LFS check) only.
What ships with it
1 file 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.
- 1mo ago Changed · +1 lines · +4 tokens per session 8d19705590b9
- 1mo ago First seen · 67 lines · 43 tokens per session scan A 31c6f17ed96f
merge-to-main is a skill published in the GitHub repository stefanrows/claude-code-plugins (3 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 2,172 once invoked, about $0.0002 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-08-31.
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
Fully automate a release with version-bump and childhood.
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.
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.
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.