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.
git clone --depth 1 https://github.com/KaelSensei/MagicAIBuilderWrote 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/commands/kaelsensei/magicaibuilder/merge-branch-into-dev)<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.
<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>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.00000 | $0.00326 |
| Opus 5 | $0.00000 | $0.00163 |
| Sonnet 5 | $0.00000 | $0.00065 |
| Haiku 4.5 | $0.00000 | $0.00033 |
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 10d 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
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).
Recommended flow (PR-first)
- Ensure local
devis 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.
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.
- 10d ago First seen · 49 lines · 0 tokens per session scan A 272629187a74
merge-branch-into-dev is a command published in the GitHub repository KaelSensei/MagicAIBuilder (2 stars, last pushed today), 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.
Other commands, from other repositories
implement-feature
Implement an approved feature plan with fresh-context slices, TDD, evidence, and PR-ready output.
review
Review code changes against project conventions.
speckit.git.commit
Proxy for speckit.git.commit.md.
speckit.git.remote
Proxy for speckit.git.remote.md.
scm
SCM workflow for Git operations (branching/merge/conflict/worktree) plus Conventional Commit execution.
prepare-release
Prepare a new release with AI-generated summary.