agentmods.dev

merge-branch-into-dev

merge-branch-into-dev is a command for Claude Code from KaelSensei/MagicAIBuilder. It costs 0 tokens per session (326 once invoked), scanned A, original, MIT.

A guided command for merging a Git branch, which is a separate line of code changes, into the shared dev branch. It includes checks for conflicts, secrets, documentation, and basic project tests.

In plain words
What is it for?
Use /merge-branch-into-dev [branch] to update dev, merge a named branch, handle conflicts, run smoke checks, and optionally push the result.
Why use it?
It reduces the chance of merging unfinished work, exposing credentials, or breaking the dev branch. It also encourages review before changes are pushed.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md). Also seen: installed under .agents/ (shared by several agents).

not rated 2repo yesterday A scan 0 tokens original MIT

Good fit Use /merge-branch-into-dev [branch] to update dev, merge a named branch, handle conflicts, run smoke checks, and optionally push the result.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/kaelsensei/magicaibuilder/merge-branch-into-dev
View source ↗ KaelSensei/MagicAIBuilder magic-ai-builder.vercel.app
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.

Clone the repo
git clone --depth 1 https://github.com/KaelSensei/MagicAIBuilder

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.

agentmods badge for merge-branch-into-dev

README.md
[![agentmods](https://agentmods.dev/badge/commands/kaelsensei/magicaibuilder/merge-branch-into-dev/github.svg)](https://agentmods.dev/commands/kaelsensei/magicaibuilder/merge-branch-into-dev)
Your own site
<a href="https://agentmods.dev/commands/kaelsensei/magicaibuilder/merge-branch-into-dev"><img src="https://agentmods.dev/badge/commands/kaelsensei/magicaibuilder/merge-branch-into-dev/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 merge-branch-into-dev

Your own site · 80×15
<a href="https://agentmods.dev/commands/kaelsensei/magicaibuilder/merge-branch-into-dev"><img src="https://agentmods.dev/badge/commands/kaelsensei/magicaibuilder/merge-branch-into-dev.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 326 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.00000 $0.00326
Opus 5.5 $0.00000 $0.00130
Sonnet 5.5 $0.00000 $0.00065
Haiku 4.5 $0.00000 $0.00033

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

Security

Grade A, and why

merge-branch-into-dev 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 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.

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.

.agents/commands/merge-branch-into-dev.md · 49 lines

What it actually says

Merge Branch Into Dev – safe merge checklist

When /merge-branch-into-dev [branch] is invoked, guide a safe merge workflow into dev.

Reference:

  • .cursor/rules/version-management.mdc
  • .cursor/rules/security.mdc
  • .cursor/rules/documentation.mdc

Safety checklist (must pass)

  • Working tree is clean (git status).
  • You know exactly what source branch you’re merging into dev.
  • No secrets are committed (private keys, mnemonics, .env, API keys, Telegram tokens, RPC tokens).
  • Config/schema/run docs updated if behavior changed (RUN_BOT/README/command docs).
  • Ensure local dev is up to date:
git fetch origin
git checkout dev
git pull --ff-only
  • Merge the branch into dev (no force pushes):
git merge --no-ff <branch-name>
  • If there are conflicts:
    • Resolve deliberately (don’t “guess” trading/sniping logic merges).
    • Re-run your minimal smoke checks (start script, import, config load).

Push (only if you explicitly intend to)

git push origin dev

Notes / rules

  • Prefer PR-based merges when possible (review + CI).
  • Avoid force-pushes to shared branches (dev, main).
  • If you see secret-like files in the diff, stop and fix .gitignore / rotate keys.
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. 2mo ago First seen · 49 lines · 0 tokens per session scan A 272629187a74

Subscribe to this mod's changes

merge-branch-into-dev is a command published in the GitHub repository KaelSensei/MagicAIBuilder (2 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 326 tokens. 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.

Git and workflowdockeredhmagic-the-gatheringnextjspostgresqlprisma
Related

merge-branch-into-dev compared with commands from other repositories

merge-branch-into-dev next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
merge-branch-into-devKaelSensei/MagicAIBuilderCommand2yesterdayMITA0Claude Code
implement-featureHoangNguyen0403/agent-skills-standardCommand583todayMITA0Claude Code
reviewvstorm-co/full-stack-ai-agent-templateCommand2.0k7d agoMITA6Claude Code
prepare-releasepaulpreibisch/AgentVibesCommand15623d agoApache-2.0A8Claude Code
scmfirst-fluke/fullstack-starterCommand2253d agoMITA21GitHub Copilot
plan-worktree-cleanupxonovex/platformCommand612d agoMITA14Claude Code
reap-prsEmbassy-of-the-Free-Mind/sourcelibrary-v2Command25todayAGPL-3.0A20Claude Code